Industry Category

Health Care / Life Sciences

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

3490 threat reports
Page 12 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 133–144 / 3490 reports
PHP2Shell: Inside the Critical Zero-Day RCE That Threatens Every PHP-Powered Website
PHP2Shell: Inside the Critical Zero-Day RCE That Threatens Every PHP-Powered Website
Internet2 weeks ago

PHP2Shell: Inside the Critical Zero-Day RCE That Threatens Every PHP-Powered Website

In October 2026, two critical unauthenticated remote code execution vulnerabilities — CVE-2026-109618 and CVE-2026-109619, both rated CVSS 9.2 — were disclosed prematurely via a Hacker News leak before the PHP security team could coordinate a patched release. Dubbed PHP2Shell, the associated exploit targets a use-after-free and memory corruption flaw in PHP's multipart/form-data handling combined with the session upload progress mechanism, affecting PHP versions 5 through 8. Widely used platforms including WordPress, Drupal, Joomla, Magento, and Laravel were demonstrated as vulnerable, with exploitation requiring no authentication. The PHP team expedited patches on October 21, 2026, but security researchers estimated mass exploitation could begin within 15 minutes of public disclosure. This incident underscores the compounding risk when vulnerability embargoes fail — turning a managed patch cycle into a zero-day race. With PHP powering an estimated 77% of server-side web applications, the blast radius of supply-chain and infrastructure exposure is extraordinary, and organizations relying on end-of-life PHP branches face unpatched risk.

Critical impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(medium)
LMLateral Movement(medium)
C&CCommand & Control(high)
EExfiltration(medium)
IImpact(medium)
Read report
CVSS 10.0: How CVE-2026-110264 Put Every GitLab Instance Since 2014 at Risk of Unauthenticated RCE
CVSS 10.0: How CVE-2026-110264 Put Every GitLab Instance Since 2014 at Risk of Unauthenticated RCE

CVSS 10.0: How CVE-2026-110264 Put Every GitLab Instance Since 2014 at Risk of Unauthenticated RCE

On October 21, 2026, GitLab disclosed CVE-2026-110264, a CVSS 10.0 critical vulnerability affecting every self-managed GitLab release from version 7.0 (2014) through 19.5, spanning twelve years of releases. The flaw resides in Onigmo, the Ruby regular-expression engine bundled within GitLab's own packages, where an integer overflow during compilation of a specially crafted regex allows an unauthenticated remote attacker to execute arbitrary code on the server. GitLab released patches across seven version branches simultaneously, including four outside its standard support window, underscoring severity. No active exploitation has been confirmed, but no interim workaround exists—patching is the only mitigation. This disclosure is the fourth unauthenticated code-execution flaw found in GitLab's regex engine within a single month by the same researcher, signaling a systemic vulnerability class in widely deployed DevOps infrastructure. With CI/CD pipelines increasingly targeted as supply-chain entry points, unpatched GitLab instances represent high-value lateral movement and exfiltration vectors for nation-state and ransomware threat actors alike.

Critical impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(medium)
LMLateral Movement(medium)
C&CCommand & Control(medium)
EExfiltration(medium)
IImpact(low)
Read report
LiteLLM Supply Chain Breach: How a Stolen OAuth Token Backdoored Your AI Stack
LiteLLM Supply Chain Breach: How a Stolen OAuth Token Backdoored Your AI Stack

LiteLLM Supply Chain Breach: How a Stolen OAuth Token Backdoored Your AI Stack

In October 2026, LiteLLM version 1.107.0 was compromised in a software supply chain attack that injected a credential stealer (privcollect) and a persistent backdoor into PyPI wheels and Docker images. Threat actors exploited stolen GitHub CLI OAuth tokens to hijack three engineers' accounts, using one to trigger a malicious release pipeline and another to approve it. The malware executed automatically at Python interpreter startup via a rogue cook.pth file, harvesting cloud tokens, private keys, browser data, AI tooling credentials, and environment variables before exfiltrating them to attacker-controlled infrastructure. All affected packages have since been quarantined on PyPI. This incident is the second confirmed supply chain compromise of LiteLLM within the same year, following the March 2026 TeamPCP campaign. The pattern signals that AI development tooling has become a high-value target for supply chain attackers, as a single compromised package can expose cloud credentials and model configurations across hundreds of downstream enterprise environments simultaneously.

Critical impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(high)
LMLateral Movement(medium)
C&CCommand & Control(high)
EExfiltration(high)
IImpact(medium)
Read report
PHP2Shell Was Being Exploited Before Anyone Knew It Existed: Lessons from Amazon MadPot
PHP2Shell Was Being Exploited Before Anyone Knew It Existed: Lessons from Amazon MadPot

PHP2Shell Was Being Exploited Before Anyone Knew It Existed: Lessons from Amazon MadPot

On October 17, 2026, Amazon Threat Intelligence detected active exploitation of PHP2Shell (CVE-2026-109618 and CVE-2026-109619) through its MadPot honeypot network — four days before public disclosure. The exploit originated from anonymized infrastructure, suggesting a threat actor obtained vulnerability details prior to the embargo lift on October 21, 2026. Within hours of the embargo expiring, multiple actors leveraging varied payloads and anonymization infrastructure began broad exploitation, indicating coordinated or parallel independent discovery. AWS's analysis of over 200 billion events per minute enabled rapid detection, but real-world systems without equivalent telemetry or accelerated patching remained exposed. This incident underscores a structural shift in the vulnerability exploitation lifecycle: AI-assisted patch diffing and advisory analysis now compress the time from disclosure to weaponization from days to hours. Security teams can no longer treat public disclosure dates as the start of their exposure window, and traditional 7-to-30-day patch SLAs are operationally obsolete for critical internet-facing systems.

High impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(medium)
LMLateral Movement(low)
C&CCommand & Control(medium)
EExfiltration(low)
IImpact(medium)
Read report
PHP Zero-Days CVE-2026-109618 & CVE-2026-109619: How 2.58 Million Hosts Became Targets Overnight
PHP Zero-Days CVE-2026-109618 & CVE-2026-109619: How 2.58 Million Hosts Became Targets Overnight
Internet2 weeks ago

PHP Zero-Days CVE-2026-109618 & CVE-2026-109619: How 2.58 Million Hosts Became Targets Overnight

In October 2026, two critical zero-day vulnerabilities in PHP—CVE-2026-109618 and CVE-2026-109619—were publicly disclosed, affecting every PHP version released over the past decade (PHP 5.4 and later). Approximately 2.58 million internet-facing hosts and 54.9 million web properties running PHP were exposed, spanning platforms including WordPress, Drupal, Joomla, and Magento. Exploitation began immediately, with Cloudflare detecting active attacks within hours of disclosure. Threat actors leveraged the flaws for remote code execution, denial-of-service conditions, and web shell installation, enabling persistent backdoor access. Government websites across Europe went offline. Emergency patches were issued in PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35. This incident echoes the 2021 Log4Shell crisis in scale and severity—a deeply embedded runtime component exploited at internet scale before most organizations could respond. AI-assisted exploit development accelerated the weaponization timeline, compressing the window between disclosure and mass exploitation and raising the bar for how quickly defenders must act across cloud, hybrid, and on-premises infrastructure.

Critical impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(medium)
LMLateral Movement(medium)
C&CCommand & Control(high)
EExfiltration(medium)
IImpact(high)
Read report
Inside the Vasilek Operation: How Cyber Partisans Hid a Backdoor in VMware Tools for Two Years
Inside the Vasilek Operation: How Cyber Partisans Hid a Backdoor in VMware Tools for Two Years

Inside the Vasilek Operation: How Cyber Partisans Hid a Backdoor in VMware Tools for Two Years

Between early 2024 and December 2025, a Belarus-aligned threat group known as Partisan Zmiy (Cyber Partisans) conducted a covert, nearly two-year espionage campaign inside a Russian healthcare organization's network. The attackers deployed the Vasilek backdoor (v1.5.8) by masquerading malicious executables as VMware Tools components—planting a rogue loader service ('vmauad') and replacing the legitimate 'vmtools.dll' with a malicious version. Vasilek leveraged Telegram for command-and-control and data exfiltration, activated GOST tunnels on a tight weekly schedule, and employed extensive operational security measures including timestomping, log clearing via 'Evlx,' and hostname binding. The group refrained from deploying its known Pryanik wiper, preserving access to exploit trusted relationships with subsidiary medical institutions. This incident exemplifies a maturing shift among hacktivist-aligned threat actors toward long-duration, low-noise espionage over destructive operations. The abuse of trusted virtualization infrastructure—specifically VMware Tools directories—to conceal persistent backdoors underscores the growing risk of supply-chain-adjacent persistence techniques in healthcare and critical infrastructure environments.

High impact

Kill Chain

ICInitial Compromise(low)
PEPrivilege Escalation(high)
LMLateral Movement(medium)
C&CCommand & Control(high)
EExfiltration(high)
IImpact(medium)
Read report
PHP2Shell: Two CVSS 9.2 RCE Zero-Days Put 884,000 Legacy PHP Hosts at Immediate Risk
PHP2Shell: Two CVSS 9.2 RCE Zero-Days Put 884,000 Legacy PHP Hosts at Immediate Risk

PHP2Shell: Two CVSS 9.2 RCE Zero-Days Put 884,000 Legacy PHP Hosts at Immediate Risk

On October 21, 2026, PHP's security team issued an emergency out-of-cycle patch for two critical remote code execution vulnerabilities—CVE-2026-109618 and CVE-2026-109619—collectively dubbed 'PHP2Shell' by the research community. Rated CVSS 9.2 under v4.0, the flaws affect all four actively supported PHP branches (8.2–8.5) and were leaked prematurely via a Hacker News post before the coordinated disclosure date. Security firm watchTowr confirmed the flaws were real and under embargo. Roughly 884,000 internet-facing hosts were identified running PHP 8.1 or older—end-of-life versions that will receive no vendor patch—placing a significant portion of the global PHP ecosystem at sustained risk of unauthenticated remote compromise. This incident underscores the compounding risk of premature vulnerability disclosure combined with a massive legacy software footprint. With PHP powering a large share of the web, the window between public knowledge and active exploitation is shrinking, and organizations running unpatched or end-of-life PHP versions face an elevated and immediate threat of web shell deployment and lateral movement across their environments.

Critical impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(medium)
LMLateral Movement(medium)
C&CCommand & Control(high)
EExfiltration(medium)
IImpact(medium)
Read report
PHP2Shell (CVE-2026-109618/109619): The Network Controls That Actually Limit Your Exposure Before 14:00 UTC
PHP2Shell (CVE-2026-109618/109619): The Network Controls That Actually Limit Your Exposure Before 14:00 UTC

PHP2Shell (CVE-2026-109618/109619): The Network Controls That Actually Limit Your Exposure Before 14:00 UTC

On October 21, 2026, PHP disclosed two critical Remote Code Execution vulnerabilities—CVE-2026-109618 and CVE-2026-109619, collectively dubbed PHP2Shell—rated 9.2/10 in severity, with an emergency patch scheduled for 14:00 UTC the same day. Prior to the patch, no vendor-confirmed workaround existed: a widely circulated mitigation involving disabling session.upload_progress was publicly walked back by its originator, GMO Flatt Security, and rejected by PHP core developers. Cloudflare observed early exploitation attempts and deployed emergency WAF rules as a stopgap. No confirmed breach was reported at disclosure, but the attack surface covered all PHP-based web applications, including WordPress and Laravel deployments, across supported branches 8.2 through 8.5. PHP2Shell underscores a recurring and dangerous pattern: high-severity zero-days in ubiquitous server-side runtimes create narrow but critical windows where unpatched internet-facing infrastructure is exposed. The incident highlights the inadequacy of configuration-level mitigations as substitutes for runtime patching, and reinforces the need for network-level controls—egress restriction, east-west segmentation, and anomaly detection—to limit blast radius during patch-gap windows.

Critical impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(medium)
LMLateral Movement(medium)
C&CCommand & Control(medium)
EExfiltration(medium)
IImpact(medium)
Read report
SafePay Ransomware: How 600+ Organizations Were Compromised Through Unpatched VPNs and Flat Networks
SafePay Ransomware: How 600+ Organizations Were Compromised Through Unpatched VPNs and Flat Networks

SafePay Ransomware: How 600+ Organizations Were Compromised Through Unpatched VPNs and Flat Networks

Since August 2024, the SafePay ransomware group has compromised at least 600 victims across critical infrastructure sectors in North America, South America, Europe, and Australia. Threat actors gain initial access by exploiting unpatched VPN and edge-device vulnerabilities—including CVE-2020-3259, CVE-2023-20269, CVE-2023-27532, CVE-2024-40711, and CVE-2024-40766—and through brute-force credential attacks using Mullvad VPN exit nodes. Once inside, actors employ living-off-the-land binaries (PsExec, WinRM, RDP), disable security tooling, escalate privileges via UAC bypass and token impersonation, and exfiltrate data with FileZilla, RClone, WinSCP, and Backblaze B2 before encrypting files with a hybrid ChaCha20/RSA scheme and demanding cryptocurrency ransoms. SafePay ranked among the most active ransomware groups in 2026, demonstrating that double-extortion operations targeting unpatched edge devices and flat, under-segmented networks remain highly effective. The group's systematic abuse of legitimate administrative tools underscores a growing industry-wide challenge: distinguishing malicious LOTL activity from routine IT operations without robust east-west visibility and zero-trust segmentation controls.

Critical impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(high)
LMLateral Movement(high)
C&CCommand & Control(high)
EExfiltration(high)
IImpact(high)
Read report
PHP2Shell: How Two Critical RCE Flaws in the PHP Runtime Expose Every Cloud Workload Running PHP
PHP2Shell: How Two Critical RCE Flaws in the PHP Runtime Expose Every Cloud Workload Running PHP

PHP2Shell: How Two Critical RCE Flaws in the PHP Runtime Expose Every Cloud Workload Running PHP

In October 2026, the PHP project issued emergency patches for two critical remote code execution vulnerabilities—CVE-2026-109618 and CVE-2026-109619, collectively dubbed PHP2Shell—rated 9.2 on the CVSS v4.0 scale. Discovered by researchers at Wiz, Calif, and OpenAI's Codex Security team, the flaws reside in the PHP runtime engine itself, meaning every web application running on a vulnerable PHP version is exposed regardless of application-level security. Attackers can execute arbitrary code without authentication, with Apache mod_php servers at highest risk. Early exploit attempts were observed by Cloudflare before patches shipped, and organizations including BambooHR and Dutch government portals took services offline as a precaution. Fixed versions are PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35. This incident underscores a growing trend of AI-assisted vulnerability research accelerating exploit development timelines from months to days. The PHP2Shell flaws affect an estimated 77% of all websites using server-side languages, making this one of the broadest-impact web infrastructure vulnerabilities in recent years and raising urgent questions about runtime-layer security hygiene.

Critical impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(high)
LMLateral Movement(medium)
C&CCommand & Control(medium)
EExfiltration(medium)
IImpact(medium)
Read report
PHP's Worst Day in Years: CVE-2026-109618 & CVE-2026-109619 Put Every Web Server at Risk
PHP's Worst Day in Years: CVE-2026-109618 & CVE-2026-109619 Put Every Web Server at Risk
Internet2 weeks ago

PHP's Worst Day in Years: CVE-2026-109618 & CVE-2026-109619 Put Every Web Server at Risk

On October 21, 2026, the PHP project released emergency patches for two critical vulnerabilities—CVE-2026-109618 and CVE-2026-109619—affecting all PHP versions from PHP 5 through the latest releases, with a combined CVSS score of 9.4. CVE-2026-109618 enables remote code execution through out-of-memory corruption via malformed multipart MIME requests that bypass post_max_size controls, while CVE-2026-109619 exploits a use-after-free condition triggered by improper global state resets between worker requests. Proof-of-concept exploits were publicly released before the patch, and Cloudflare confirmed active in-the-wild exploitation within hours of disclosure. Organizations running PHP-based web applications—covering an estimated 77% of all server-side web infrastructure—faced immediate, widespread exposure. This incident underscores the systemic risk of pre-patch PoC availability colliding with mass-deployed open-source runtimes. The combination of unauthenticated remote code execution, a massive attack surface, and rapid weaponization mirrors the Log4Shell pattern, reinforcing the urgency of runtime traffic inspection and egress controls as compensating measures when patch cycles lag exploit availability.

Critical impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(medium)
LMLateral Movement(medium)
C&CCommand & Control(medium)
EExfiltration(medium)
IImpact(medium)
Read report
22.6 Million PHP Instances at Risk: What Security Teams Must Do Now About CVE-2026-109618 and CVE-2026-109619
22.6 Million PHP Instances at Risk: What Security Teams Must Do Now About CVE-2026-109618 and CVE-2026-109619
Internet2 weeks ago

22.6 Million PHP Instances at Risk: What Security Teams Must Do Now About CVE-2026-109618 and CVE-2026-109619

In October 2026, Unit 42 researchers disclosed two critical remote code execution vulnerabilities in PHP—CVE-2026-109618 and CVE-2026-109619—each carrying a CVSS 4.0 score of 9.2. CVE-2026-109618 exploits improper control flow in out-of-memory error handling via longjmp(), leaving request memory uninitialized and enabling reliable RCE through OOM triggers. CVE-2026-109619 allows attackers to read or branch on freed global memory during subsequent requests, also achieving arbitrary code execution. Palo Alto Networks Cortex Xpanse identified over 22.6 million potentially exposed instances globally, and at least one European government proactively took its public website offline. Proof-of-concept code has been observed by Unit 42 researchers, indicating active weaponization risk. These vulnerabilities reflect a broadening attacker focus on foundational web runtime environments rather than application-layer logic alone. As PHP continues to underpin millions of web servers and content management systems worldwide, critical runtime flaws like these represent a systemic risk that demands immediate patching, attack surface management, and inline threat prevention—particularly as autonomous vulnerability discovery tools lower the bar for exploitation at scale.

Critical impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(medium)
LMLateral Movement(medium)
C&CCommand & Control(medium)
EExfiltration(medium)
IImpact(high)
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