Industry Category

Health Care / Life Sciences

Breach intelligence, attack campaigns, and threat reports targeting the Health Care / Life Sciences sector.

3490 threat reports
Page 9 of 291
Explore Other Sectors
AccountingAerospaceAerospace/AviationAgricultureAirlines/AviationAnimationApparel/FashionArchitecture/PlanningArtificial IntelligenceArtificial Intelligence/Machine LearningArts/CraftsAutomotiveAviation/AerospaceBanking/MortgageBiotechnology/GreentechBlockchain/CryptocurrencyBroadcast MediaBroadcasting MediaBroadcasting/MediaBuilding MaterialsBusiness Supplies/EquipmentCapital Markets/Hedge Fund/Private EquityChemicalChemicalsCivic/Social OrganizationCivil EngineeringCloud ComputingCloud Computing/SaaSCloud Native Security Fabric (CNSF)Cloud ServicesCommercial FacilitiesCommercial Real EstateComputer GamesComputer HardwareComputer NetworkingComputer Software/EngineeringComputer/Network SecurityConstructionConsultingConsumer ElectronicsConsumer GoodsConsumer ServicesCosmeticsCosmeticsCritical ManufacturingCryptocurrenciesCryptocurrencyCustomer ServicesCybersecurityDairyDating/Personal ServicesDating/Social PlatformsDefense/SpaceDesignE-LearningEducation ManagementElectrical/Electronic ManufacturingEmergency ServicesEnergyEnergy/Oil/Solar/GreentechEntertainment/Movie ProductionEnvironmental ServicesEvents ServicesExecutive OfficeFacilities ServicesFarmingFashion/ApparelFinancial ServicesFine ArtFisheryFood ProductionFood/BeveragesFortune 500 companiesFranchisingFundraisingGambling/CasinosGamingGaming/CasinosGovernment AdministrationGovernment FacilitiesGovernment RelationsGraphic Design/Web DesignHealth Care / Life SciencesHealthcareHigher Education/AcadamiaHospitalityHospitalsHuman Resources/HRImport/ExportIndividual/Family ServicesIndustrial AutomationInformation ServicesInformation Technology/ITInsuranceInternational AffairsInternational Trade/DevelopmentInternetInvestment Banking/VentureInvestment Management/Hedge Fund/Private EquityJudicialJudiciaryLaw EnforcementLaw Practice/Law FirmsLegal ServicesLegislative OfficeLeisure/TravelLogistics/ProcurementLuxury Goods/JewelryMachineryManagement ConsultingManufacturingMaritimeMarket ResearchMarketing/Advertising/SalesMechanical or Industrial EngineeringMedia ProductionMedical EquipmentMedical PracticeMilitary IndustryMining/MetalsMobileMuseums/InstitutionsMusicNewspapers/JournalismNon-Profit/VolunteeringOil/Energy/Solar/GreentechOnline PublishingOther IndustryOutsourcing/OffshoringPackage/Freight DeliveryParkingPharmaceuticalsPhilanthropyPhotographyPlasticsPolitical OrganizationPrimary/Secondary EducationProfessional ServicesProfessional TrainingPublic Relations/PRPublic SafetyPublishing IndustryRailroad ManufactureReal Estate/MortgageRecreational Facilities/ServicesReligious InstitutionsRenewables/EnvironmentResearch IndustryRestaurantsRetail IndustryRoboticsRural HealthcareSecurity/InvestigationsSemiconductorsShipbuildingSocial Media/InternetSporting GoodsSportsStaffing/RecruitingSupermarketsTechnologyTechnology/ITTelecommunicationsThink TanksToys and GamesTransportationTravel/TourismTrucking/FreightUtilitiesVenture Capital/VCWarehousingWater and Waste ManagementWater and WastewaterWater and Wastewater SystemsWater and Wastewater TreatmentWater TreatmentWater, Waste, Steam, and Air Conditioning ServicesWater/Waste ManagementWater/WastewaterWater/Wastewater ManagementWater/Wastewater/UtilitiesWholesaleWine/SpiritsWirelessWriting/Editing

Health Care / Life Sciences Threat Reports

Showing 97–108 / 3490 reports
When IT Support Becomes the Threat: How Attackers Weaponized Microsoft Teams to Deploy Chaos Ransomware
When IT Support Becomes the Threat: How Attackers Weaponized Microsoft Teams to Deploy Chaos Ransomware

When IT Support Becomes the Threat: How Attackers Weaponized Microsoft Teams to Deploy Chaos Ransomware

Beginning in 2026, threat actors exploiting Microsoft Teams' external chat feature launched a sophisticated social engineering campaign impersonating IT support personnel to deliver malware and ransomware across hundreds of organizations. Attackers established fraudulent Microsoft 365 tenants using IT-themed onmicrosoft.com and paid top-level domains, preceded attacks with email bombing to create urgency, then used vishing to gain remote access via tools such as AnyDesk, Quick Assist, and Atera. Once inside, they conducted Active Directory reconnaissance via LDAP queries, deployed the GoGRPC backdoor, moved laterally to domain controllers, and dropped Chaos ransomware while exfiltrating sensitive data. This campaign underscores a critical shift in attacker tradecraft: rather than exploiting software vulnerabilities, adversaries are weaponizing trusted collaboration platforms and legitimate remote management tools. The STAC4749 threat cluster's repeated use of this pattern—across cloud tenants, RMM tooling, and ransomware payloads—signals a durable, scalable playbook that security teams must treat as an ongoing threat to enterprise communication infrastructure.

Critical impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(high)
LMLateral Movement(high)
C&CCommand & Control(high)
EExfiltration(high)
IImpact(high)
Read report
Token Spraying: How Attackers Bypassed MFA and Compromised 97 Microsoft 365 Accounts Across 79 Organizations
Token Spraying: How Attackers Bypassed MFA and Compromised 97 Microsoft 365 Accounts Across 79 Organizations

Token Spraying: How Attackers Bypassed MFA and Compromised 97 Microsoft 365 Accounts Across 79 Organizations

Between July 14 and September 22, 2026, threat actors executed a large-scale adversary-in-the-middle (AitM) token-replay campaign against Microsoft 365, compromising 97 accounts across 79 organizations from more than 200,000 login attempts. Attackers deployed fake Microsoft sign-in pages to harvest session tokens and MFA codes in real time, then replayed those tokens within minutes from infrastructure tied to Romanian and German hosting provider 1337 Services GmbH. Post-access persistence was achieved by registering 48 rogue Entra devices, hijacking MFA methods, and planting hidden inbox rules to intercept payroll and finance-related emails—enabling business email compromise at scale. This campaign illustrates the accelerating shift away from password-based attacks toward token-based identity exploitation, where MFA alone provides insufficient protection. As AitM phishing kits become commoditized and token-spraying techniques proliferate, organizations relying solely on perimeter defenses and standard MFA face compounding exposure across cloud identity platforms.

High impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(high)
LMLateral Movement(high)
C&CCommand & Control(medium)
EExfiltration(high)
IImpact(medium)
Read report
Everything's an RCE: PHP2Shell, LiteLLM Supply Chain, and Rogue AI Agents Define a Record-Breaking Threat Week
Everything's an RCE: PHP2Shell, LiteLLM Supply Chain, and Rogue AI Agents Define a Record-Breaking Threat Week

Everything's an RCE: PHP2Shell, LiteLLM Supply Chain, and Rogue AI Agents Define a Record-Breaking Threat Week

In the week of October 26, 2026, a convergence of critical remote code execution vulnerabilities, supply chain compromises, and AI-driven attacks created an unprecedented threat landscape. PHP2Shell (CVE-2026-109618/109619) triggered millions of exploitation attempts, while a leaked LiteLLM master key enabled a malicious Python package that harvested credentials across developer environments. Agentic AI platforms were weaponized by four newly identified threat actor groups using Claude Code to exfiltrate healthcare and government data. CISA added Plex2Shell flaws to its KEV catalog, and ransomware attacks surged 50% quarter-over-quarter, underscoring systemic exposure across web infrastructure, open-source dependencies, and AI tooling. This week's events reflect a structural acceleration in attacker capabilities: AI is now operationally embedded in offensive campaigns, the exploitation window for high-severity CVEs has shrunk to three days, and supply chain trust is being exploited through leaked keys and poisoned packages. Organizations relying on legacy patch cadences or perimeter-only defenses are increasingly unable to contain threats that propagate laterally through cloud and AI workloads before detection occurs.

Critical impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(high)
LMLateral Movement(high)
C&CCommand & Control(high)
EExfiltration(high)
IImpact(high)
Read report
Tailworm 2026: How One Hacked Device Can Root Your Entire Tailscale Mesh Network
Tailworm 2026: How One Hacked Device Can Root Your Entire Tailscale Mesh Network

Tailworm 2026: How One Hacked Device Can Root Your Entire Tailscale Mesh Network

In October 2026, security researcher Erica Windisch of Cyberdione Labs published the Tailworm report detailing critical unpatched vulnerabilities in Tailscale SSH (version 1.104.2) and headscale (version 0.29.5). The research demonstrated that a single compromised device within a Tailscale zero-trust mesh network could escalate privileges to root on any reachable server in under a second per hop, requiring no stolen credentials or user interaction. Three distinct exploitation paths were identified—Unix socket abuse, socket substitution, and a time-of-check/time-of-use race condition—enabling fleet-wide lateral movement. As of publication, no patch, CVE, or security bulletin had been issued by Tailscale. This incident underscores a dangerous assumption embedded in zero-trust architectures: that device-identity-based access implicitly prevents privilege escalation. As organizations accelerate adoption of mesh VPN and software-defined networking tools to replace perimeter security, unvalidated trust in lateral SSH paths creates wormable blast radii that traditional segmentation and firewall controls may not contain.

Critical impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(high)
LMLateral Movement(high)
C&CCommand & Control(medium)
EExfiltration(medium)
IImpact(medium)
Read report
PHP2Shell: How Two Critical PHP RCE Bugs Sent the Security Industry Into Red-Alert Mode
PHP2Shell: How Two Critical PHP RCE Bugs Sent the Security Industry Into Red-Alert Mode

PHP2Shell: How Two Critical PHP RCE Bugs Sent the Security Industry Into Red-Alert Mode

In October 2026, two critical remote code execution vulnerabilities in PHP—CVE-2026-109618 and CVE-2026-109619, collectively dubbed 'PHP2Shell'—were disclosed with a CVSS v4.0 score of 9.2. Discovered by infosec firm Calif and analyzed by WatchTowr, both flaws allow unauthenticated attackers to execute arbitrary code on web servers simply by reaching them over the network. An embargo break led to early publication of a proof-of-concept tool, accelerating attacker reconnaissance while defenders scrambled to patch or mitigate across Apache mod_php, PHP-FPM, php-cgi, FrankenPHP, and LiteSpeed deployments. Active exploitation attempts were observed in the wild within hours of disclosure. The PHP2Shell incident echoes Log4Shell in scope and urgency, underscoring the fragility of open source supply chains and the disproportionate risk carried by under-resourced organizations—schools, municipalities, and nonprofits—that lack dedicated security staff but run PHP-based infrastructure extensively exposed to the internet.

Critical impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(medium)
LMLateral Movement(medium)
C&CCommand & Control(medium)
EExfiltration(medium)
IImpact(high)
Read report
PHP2Shell Exploitation Surge: What Security Teams Must Do Now About CVE-2026-109618 and CVE-2026-109619
PHP2Shell Exploitation Surge: What Security Teams Must Do Now About CVE-2026-109618 and CVE-2026-109619

PHP2Shell Exploitation Surge: What Security Teams Must Do Now About CVE-2026-109618 and CVE-2026-109619

In October 2026, two critical PHP remote code execution vulnerabilities—CVE-2026-109618 and CVE-2026-109619, collectively dubbed PHP2Shell—triggered a global exploitation wave within hours of public disclosure. Cloudflare observed thousands of exploit attempts in the 10 hours before announcement, escalating to millions within two hours post-disclosure. Check Point Research reported that 10% of organizations worldwide faced exploitation attempts within 24 hours. Complicating response efforts, over 99% of discoverable PHP instances had not patched within the first day, and roughly 73% ran unsupported PHP branches, leaving attackers a vast, largely undefended attack surface across web servers, storage appliances, cameras, and physical access-control systems. PHP2Shell underscores a persistent and worsening gap between attacker speed and enterprise patch velocity. As organizations increasingly rely on containerized, hybrid, and multi-cloud deployments, unpatched PHP surfaces embedded in firmware, legacy applications, and third-party software create systemic risk. The incident highlights why runtime network controls, east-west segmentation, and egress enforcement are essential complements to patching programs—especially when patches cannot be applied instantly or at all.

Critical impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(medium)
LMLateral Movement(medium)
C&CCommand & Control(medium)
EExfiltration(medium)
IImpact(medium)
Read report
CVE-2026-111497: The Brotli Decoder Flaw That Put Node.js, Bun, and Python at Risk of Remote Code Execution
CVE-2026-111497: The Brotli Decoder Flaw That Put Node.js, Bun, and Python at Risk of Remote Code Execution

CVE-2026-111497: The Brotli Decoder Flaw That Put Node.js, Bun, and Python at Risk of Remote Code Execution

In October 2026, a critical memory-corruption vulnerability (CVE-2026-111497) was disclosed in Google's Brotli decoder library, affecting a wide range of software including Node.js, Bun, Python Brotli packages, Envoy, and Istio. The flaw, rated CVSS 4.0 score of 9.2 by Google, allows crafted Brotli-compressed data to overwrite memory boundaries, enabling potential remote code execution, crashes, or memory leaks. Imperva's Red Team demonstrated unauthenticated RCE on an unpatched Node.js 24.22.0 build. Patches were released on October 21, 2026, but each affected product must independently update its bundled copy of the decoder. No in-the-wild exploitation had been confirmed as of initial disclosure. This supply-chain vulnerability illustrates the systemic risk of widely-shared C library code embedded across language runtimes, proxies, and package ecosystems. As organizations increasingly rely on microservices and API-driven architectures, a single upstream flaw can propagate silently across hundreds of services, making runtime network policy enforcement and egress controls essential complements to patching workflows.

Critical impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(medium)
LMLateral Movement(medium)
C&CCommand & Control(medium)
EExfiltration(medium)
IImpact(medium)
Read report
Inside the LiteLLM 1.107.0 Supply Chain Attack: How PRIVCOLLECT Stole Cloud and AI Credentials via Python Startup Hooks
Inside the LiteLLM 1.107.0 Supply Chain Attack: How PRIVCOLLECT Stole Cloud and AI Credentials via Python Startup Hooks

Inside the LiteLLM 1.107.0 Supply Chain Attack: How PRIVCOLLECT Stole Cloud and AI Credentials via Python Startup Hooks

On October 21, 2026, attackers published a malicious LiteLLM 1.107.0 release to PyPI after abusing stolen developer GitHub credentials to hijack the upstream release workflow. The compromised wheel silently planted Python startup files—cook.pth, cook.py, and sitecustomize.py—outside the application directory, causing a credential-harvesting payload (PRIVCOLLECT) to execute automatically whenever Python initialized in any affected environment, including developer workstations, CI/CD agents, containers, and AI gateway hosts. Collected credentials were AES-256-CBC encrypted, RSA-key-wrapped, and exfiltrated to an attacker-controlled domain, while a secondary Unix loader enabled dynamic remote code execution via a GitHub-hosted dead-drop pointer. This incident illustrates how a single compromised open-source dependency can silently harvest cloud credentials, AI model-provider API keys, SSH keys, and browser secrets across an entire organization's software supply chain—without the application ever being actively invoked. The growing reliance on AI gateway libraries like LiteLLM in production environments amplifies the blast radius significantly.

Critical impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(high)
LMLateral Movement(medium)
C&CCommand & Control(high)
EExfiltration(high)
IImpact(medium)
Read report
php2shell Exposed: Why This PHP RCE Exploit Is Harder to Pull Off Than the Hype Suggests
php2shell Exposed: Why This PHP RCE Exploit Is Harder to Pull Off Than the Hype Suggests
Internet2 weeks ago

php2shell Exposed: Why This PHP RCE Exploit Is Harder to Pull Off Than the Hype Suggests

In October 2024, the cybersecurity community reacted urgently to the disclosure of a PHP vulnerability nicknamed 'php2shell,' which theoretically enables remote code execution through a complex heap manipulation chain. Analysis by SANS ISC researcher Bojan revealed that reliable, weaponized exploitation is significantly harder than initial reports suggested. A working exploit requires precise memory pressure conditions, a single-worker Apache prefork configuration, knowledge of libphp.so offsets to defeat ASLR, and commands limited to 14 bytes—conditions rarely met in production environments with default 128 MB memory limits and multi-worker setups. Organizations are advised to set session.upload_progress.enabled=0 immediately as a mitigation. This incident highlights the growing challenge of accurately triaging vulnerability severity in real-world cloud and hybrid environments. As AI-generated proof-of-concept code floods public repositories, security teams face increasing noise in distinguishing theoretical exploitability from practical risk—making network-level controls and rapid configuration hardening essential layers of defense.

Critical impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(medium)
LMLateral Movement(medium)
C&CCommand & Control(medium)
EExfiltration(low)
IImpact(low)
Read report
Eight Max-Severity ArubaOS Flaws Expose Enterprise Wireless Infrastructure to Unauthenticated RCE
Eight Max-Severity ArubaOS Flaws Expose Enterprise Wireless Infrastructure to Unauthenticated RCE

Eight Max-Severity ArubaOS Flaws Expose Enterprise Wireless Infrastructure to Unauthenticated RCE

In October 2026, Hewlett Packard Enterprise released emergency security patches addressing 72 vulnerabilities in ArubaOS (AOS), the operating system powering Aruba Networking enterprise wireless infrastructure including mobility conductors, access points, controllers, and gateway devices. Eight of these flaws carry maximum CVSS severity scores and enable unauthenticated remote code execution and authentication bypass across both AOS-8 and AOS-10 software versions. The vulnerabilities—spanning command injection, SQL injection, and buffer overflow vectors—require no privileges and no user interaction, making them trivially exploitable at scale across HPE's installed base of over 55,000 enterprise customers, including 90% of Fortune 500 companies. HPE confirmed no active exploitation or public proof-of-concept code existed at time of disclosure. This disclosure follows a pattern of critical HPE network infrastructure vulnerabilities in 2025–2026, including StoreOnce auth bypass flaws, hardcoded Aruba credentials, and actively exploited HPE OneView weaknesses flagged by CISA. Attackers increasingly target network infrastructure operating systems as a high-leverage initial access vector, making unpatched edge devices a primary risk surface for enterprise environments.

Critical impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(high)
LMLateral Movement(medium)
C&CCommand & Control(medium)
EExfiltration(medium)
IImpact(medium)
Read report
PHP CVE-2026-115560: How to Defend Against an Unpatched RCE Vulnerability Targeting Millions of Web Servers
PHP CVE-2026-115560: How to Defend Against an Unpatched RCE Vulnerability Targeting Millions of Web Servers
Internet2 weeks ago

PHP CVE-2026-115560: How to Defend Against an Unpatched RCE Vulnerability Targeting Millions of Web Servers

In October 2026, the PHP security team disclosed CVE-2026-115560, a remote code execution vulnerability affecting PHP installations with non-default session serialization configurations. Exploitable only when session.serialize_handler is switched at runtime before session_start() with upload progress enabled, the flaw carries high severity despite its conditional nature. No patch was immediately available; mitigation required disabling session.upload_progress.enabled. This disclosure followed emergency patches for two related critical RCE flaws, CVE-2026-109618 and CVE-2026-109619 (collectively PHP2Shell), which were already seeing broad exploitation attempts across millions of exposed PHP hosts globally before patches were released. This incident underscores accelerating attacker timelines against unpatched web infrastructure. With over 5.1 million PHP hosts exposed online and exploitation of PHP2Shell beginning four days before patches shipped, organizations running PHP-based applications face shrinking windows between disclosure and active compromise, demanding proactive mitigation and network-layer controls beyond patch cycles alone.

Critical impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(medium)
LMLateral Movement(medium)
C&CCommand & Control(high)
EExfiltration(medium)
IImpact(medium)
Read report
AI-Executed Ransomware: Inside the Phantom Framework That Automated Intrusions Across 62 Organizations
AI-Executed Ransomware: Inside the Phantom Framework That Automated Intrusions Across 62 Organizations

AI-Executed Ransomware: Inside the Phantom Framework That Automated Intrusions Across 62 Organizations

In October 2026, cybersecurity researchers at SOCRadar exposed a sophisticated AI-driven intrusion ecosystem operated by affiliates of the INC and The Gentlemen ransomware groups. The operation centered on an autonomous framework called Phantom, which used OpenCode and commercial AI models via OpenRouter to execute human-approved but AI-automated kill chains. Attackers exploited edge devices including FortiClient EMS, SimpleHelp, cPanel, and VPN gateways using multiple CVEs, then moved laterally, harvested credentials, and exfiltrated sensitive data via reverse-SOCKS tunnels before deploying ransomware. Approximately 62 organizations were targeted, with over 50% based in the United States, primarily across industrial, manufacturing, energy, healthcare, and pharmaceutical sectors. This incident signals a structural shift in the ransomware threat landscape: AI agents are now operationalizing intrusion playbooks at machine speed while keeping humans in an approver role. The use of WormGPT-MCP, Ghost C2, and AI-curated victim knowledge bases indicates that agentic AI is rapidly becoming a standard component of ransomware-as-a-service toolkits, compressing attacker timelines and raising the bar for enterprise defenders.

High impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(high)
LMLateral Movement(high)
C&CCommand & Control(high)
EExfiltration(high)
IImpact(medium)
Read report
[ INCIDENT RESPONSE // UNDER ATTACK? ]

Stop Active Cloud Data Exfiltration

Aviatrix Rapid Containment helps teams instantly identify what data is leaving the environment, from which workload, and where it’s going — during an active breach.

Looking for threats in a different sector?

Browse All Threat Reports