Industry Category

Health Care / Life Sciences

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

3490 threat reports
Page 10 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 109–120 / 3490 reports
PHP2Shell: Millions of Exploit Attempts Targeting Critical PHP RCE Flaws to Deploy Mirai's Potassium Botnet
PHP2Shell: Millions of Exploit Attempts Targeting Critical PHP RCE Flaws to Deploy Mirai's Potassium Botnet

PHP2Shell: Millions of Exploit Attempts Targeting Critical PHP RCE Flaws to Deploy Mirai's Potassium Botnet

In October 2026, threat actors launched millions of exploitation attempts against two critical PHP vulnerabilities—CVE-2026-109618 and CVE-2026-109619 (CVSS 9.2)—targeting unauthenticated remote code execution via crafted HTTP requests. Attackers attempted to deploy the Mirai-derived Potassium botnet, which uses ChaCha20-encrypted configuration, ENS-based C2 resolution, and supports 24 DDoS flood commands across ICMP, TCP, UDP, and OpenVPN protocols. Cloudflare observed hundreds of thousands of exploit attempts within two hours of public disclosure, escalating to millions by October 22. Over 34.4 million PHP services remained vulnerable as of October 23, prompting precautionary shutdowns of government, hospital, and school websites across Asia, Europe, and North America. PHP2Shell is drawing comparisons to Log4Shell due to its deep engine-level origin dating to PHP 5.4 (2012), meaning no application-layer fix suffices. With 56.6 million web properties running PHP and patches unavailable for end-of-life branches, organizations face a prolonged exposure window. The rise of ASLR-bypass techniques and automated exploit toolkits signals escalating attacker sophistication targeting cloud-hosted and shared-hosting PHP environments.

Critical impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(medium)
LMLateral Movement(medium)
C&CCommand & Control(high)
EExfiltration(medium)
IImpact(high)
Read report
CVE-2026-112900: How a Crafted Filename Turns Python's Most Popular Image Library Into a Remote Code Execution Risk
CVE-2026-112900: How a Crafted Filename Turns Python's Most Popular Image Library Into a Remote Code Execution Risk

CVE-2026-112900: How a Crafted Filename Turns Python's Most Popular Image Library Into a Remote Code Execution Risk

In October 2026, security researchers at OX Security disclosed three critical vulnerabilities in Pillow, Python's most widely used image processing library, downloaded approximately 436 million times per month. The most severe flaw, CVE-2026-112900 (CVSS 9.2), allows remote code execution via crafted EPS filenames passed unsanitized to Ghostscript, enabling an attacker who controls a filename to execute arbitrary OS commands on the server. Two additional critical flaws affect JPEG (FPX format) and TIFF in-memory processing pipelines. All three were patched in Pillow 13.0.0 released October 16, 2026. No active exploitation has been confirmed, though a proof-of-concept exists for the TIFF flaw. These vulnerabilities are emblematic of a broader supply-chain risk pattern: a single transitive dependency embedded across web upload forms, ML pipelines, document processors, and container images can silently expose thousands of applications. As AI-assisted vulnerability research (demonstrated here by Anthropic's Claude) accelerates flaw discovery, organizations must treat open-source image libraries as high-priority attack surface in their software supply chain programs.

Critical impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(medium)
LMLateral Movement(medium)
C&CCommand & Control(medium)
EExfiltration(medium)
IImpact(low)
Read report
70,000 Credentials Stolen: How Threat Actor k0t Industrialized Enterprise Firewall and VPN Exploitation in 2026
70,000 Credentials Stolen: How Threat Actor k0t Industrialized Enterprise Firewall and VPN Exploitation in 2026

70,000 Credentials Stolen: How Threat Actor k0t Industrialized Enterprise Firewall and VPN Exploitation in 2026

Between February and June 2026, a threat actor tracked as k0t (aliases: CryptoFeel, Member19, QazWsxShop) executed a large-scale credential harvesting campaign against internet-exposed Fortinet FortiGate and Palo Alto Networks GlobalProtect devices worldwide. Leveraging public scanning tools such as FOFA and ZoomEye, k0t enumerated vulnerable edge appliances and exploited CVE-2025-64446 (FortiWeb path traversal) and CVE-2026-0257 (PAN-OS authentication bypass) via bespoke Python scripts. Post-exploitation actions included Active Directory enumeration, persistence via MeshCentral, Atera, and AnyDesk, and data exfiltration through Rclone to Wasabi S3 and MEGA. Over 70,000 credentials were harvested, with victims spanning Asia Pacific, Latin America, Europe, and MENA. This campaign underscores the accelerating role of initial access brokers (IABs) feeding ransomware groups such as Qilin and The Gentlemen. With edge device exploitation now industrialized through automated scanning and off-the-shelf exploit scripts, organizations relying solely on perimeter firewalls face systemic credential exposure risk—making zero trust segmentation and encrypted east-west traffic controls critically urgent.

Critical impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(high)
LMLateral Movement(high)
C&CCommand & Control(high)
EExfiltration(high)
IImpact(medium)
Read report
PHP RCE Vulnerability 2024: What Executives Need to Know Before Mass Exploitation Begins
PHP RCE Vulnerability 2024: What Executives Need to Know Before Mass Exploitation Begins

PHP RCE Vulnerability 2024: What Executives Need to Know Before Mass Exploitation Begins

In October 2024, SANS Internet Storm Center elevated its Infocon alert level in response to a critical PHP vulnerability affecting a broad range of web-facing applications, embedded devices, and appliances. The flaw—tied to PHP's session.upload_progress mechanism—enabled remote code execution, prompting coordinated disclosure across vendors including Cloudflare and Amazon, both of which reported large volumes of exploit attempts in the wild. Although no fully weaponized public exploit was confirmed at time of publication, security researchers warned that working exploit code was imminent. Patches were issued by php.net and major vendors, but incomplete coverage of embedded and legacy devices left significant attack surface exposed. This incident highlights a growing pattern of critical web-runtime vulnerabilities being exploited before organizations can fully patch their environments. The coordinated disclosure process succeeded, yet unpatched embedded devices and delayed enterprise patch cycles continue to represent systemic risk—underscoring why network segmentation and east-west traffic controls are essential backstops when software updates cannot be applied immediately.

Critical impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(medium)
LMLateral Movement(medium)
C&CCommand & Control(medium)
EExfiltration(medium)
IImpact(low)
Read report
OAuth Under Siege: How Attackers Hijack Tokens, Bypass MFA, and Persist Inside Enterprise Environments
OAuth Under Siege: How Attackers Hijack Tokens, Bypass MFA, and Persist Inside Enterprise Environments

OAuth Under Siege: How Attackers Hijack Tokens, Bypass MFA, and Persist Inside Enterprise Environments

As enterprises broadly adopted multi-factor authentication, adversaries pivoted from stealing passwords to harvesting OAuth tokens—the short-lived but often misconfigured credentials that govern application-level access. Unit 42 researchers documented in October 2026 how three attack classes—account hijacking via device authorization flow abuse, permission hijacking through consent-screen impersonation, and malicious OAuth redirect weaponization—now enable attackers to bypass MFA entirely, survive password resets, and maintain durable access to enterprise environments. PhaaS toolkits, LLM-generated brand impersonations, and dynamic runtime evasion have industrialized these campaigns, lowering attacker skill requirements while dramatically raising organizational risk. OAuth token hijacking represents a structural shift in the identity threat landscape: attackers no longer need to defeat authentication controls because they operate entirely in the authorization layer. With OAuth adoption expanding into critical infrastructure platforms such as Cloudflare DNS and CDN routing, the blast radius of a single compromised consent event has grown substantially, making token governance and admin-only consent workflows urgent enterprise priorities.

High impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(high)
LMLateral Movement(high)
C&CCommand & Control(medium)
EExfiltration(high)
IImpact(medium)
Read report
eMudhra Intermediate CA Compromise: When Weak Entropy Breaks the Entire Chain of Trust
eMudhra Intermediate CA Compromise: When Weak Entropy Breaks the Entire Chain of Trust

eMudhra Intermediate CA Compromise: When Weak Entropy Breaks the Entire Chain of Trust

In October 2026, Palo Alto Networks Unit 42 disclosed that eight intermediate certificate authority (CA) private keys belonging to Indian CA eMudhra Limited were compromised due to a critical cryptographic defect introduced during certificate generation. Insufficient entropy during key generation allowed attackers to mathematically derive private keys directly from the corresponding public certificates. With access to these keys, adversaries could sign unauthorized TLS certificates, enabling meddler-in-the-middle (MitM) traffic interception, domain impersonation, and session hijacking across any domain protected by eMudhra-issued certificates. Major browser and OS vendors moved swiftly to revoke trust in the affected intermediates, and eMudhra revoked all eight certificates. This incident underscores the fragility of global PKI trust hierarchies and the cascading risk posed by a single CA's cryptographic failure. As certificate lifespans compress to 47 days and supply-chain attacks targeting cryptographic infrastructure grow more frequent, organizations must adopt automated certificate lifecycle management and continuous CT log monitoring to detect and respond to unauthorized certificate issuance before adversaries exploit it.

High impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(medium)
LMLateral Movement(medium)
C&CCommand & Control(medium)
EExfiltration(high)
IImpact(high)
Read report
When the Lock Is Made of Paper: The eMudhra TLS Certificate Meltdown of 2026
When the Lock Is Made of Paper: The eMudhra TLS Certificate Meltdown of 2026
Banking/Mortgage2 weeks ago

When the Lock Is Made of Paper: The eMudhra TLS Certificate Meltdown of 2026

In October 2026, Indian Certificate Authority eMudhra Limited was found to have issued eight TLS certificates bearing catastrophically weak private keys, ranging from just 3 to 8 bits of entropy instead of the standard 384 bits required for NIST P-384 elliptic curve cryptography. The defect, likely introduced through misconfigured or example key-generation code promoted to production, rendered the certificates trivially breakable by any adversary capable of mounting a man-in-the-middle position. VPN users, non-browser TLS clients, and any relying party that trusted eMudhra's root were immediately exposed to potential traffic interception and decryption. Certificate Transparency logs surfaced the anomaly, but only after issuance, underscoring the reactive nature of current PKI oversight mechanisms. This incident arrives amid a broader wave of PKI supply-chain failures and state-sponsored traffic-interception campaigns such as Salt Typhoon, highlighting that the integrity of encrypted communications depends entirely on the rigor of every CA in the trust store. Regulators and enterprises are now under pressure to enforce continuous CT-log monitoring, automate certificate validation pipelines, and adopt network-layer encryption that does not rely solely on TLS certificate trust.

Critical impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(medium)
LMLateral Movement(medium)
C&CCommand & Control(medium)
EExfiltration(high)
IImpact(medium)
Read report
When 15 Seconds Is All It Takes: Machine Speed Attacks Demand Autonomous Response
When 15 Seconds Is All It Takes: Machine Speed Attacks Demand Autonomous Response

When 15 Seconds Is All It Takes: Machine Speed Attacks Demand Autonomous Response

In 2026, Exaforce documented a surge of sub-15-minute identity-driven attacks across enterprise environments. Three distinct patterns emerged: dormant OAuth tokens stolen from developer laptops via poisoned npm packages or infostealers were later weaponized to exfiltrate GitHub repositories at machine speed; ClickFix lures impersonating AI tool installers (Claude Code) deployed macOS stealers that harvested browser cookies and cloud credentials; and vishing campaigns mimicking IT help desks manipulated employees into approving real MFA prompts, granting attackers full session access within minutes. In one GitHub token case, 472 of 638 repositories were exfiltrated in under 15 seconds before containment actions could be authorized. These incidents expose a structural gap in enterprise security: detection platforms and identity providers flag anomalies but rely on human approval for response actions, leaving a critical window attackers now routinely exploit. The convergence of AI-lure social engineering, long-lived OAuth tokens, and incomplete session revocation across SaaS ecosystems signals a new normal where autonomous, low-friction response automation is no longer optional.

Critical impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(high)
LMLateral Movement(high)
C&CCommand & Control(high)
EExfiltration(high)
IImpact(high)
Read report
LiteLLM's Poisoned Pipeline: How Attackers Weaponized an AI Gateway to Steal Cloud and Developer Secrets
LiteLLM's Poisoned Pipeline: How Attackers Weaponized an AI Gateway to Steal Cloud and Developer Secrets

LiteLLM's Poisoned Pipeline: How Attackers Weaponized an AI Gateway to Steal Cloud and Developer Secrets

On October 21, 2026, attackers compromised the LiteLLM project's release pipeline and published malicious version 1.107.0 to PyPI and Docker Hub. The tampered package contained an info-stealer that harvested cloud credentials (AWS, Azure, GCP, Kubernetes), AI provider secrets, developer keys, browser data, and environment variables, encrypting the haul with AES-256-CBC under an RSA-4096 key before exfiltrating it to a threat-actor-controlled endpoint. All seven PyPI wheels and four Docker image tags were affected for roughly two hours before removal. Organizations running LiteLLM in production—including high-profile users such as NVIDIA, Netflix, AT&T, and Okta—were at risk of full secrets compromise across their AI infrastructure. This incident is the second supply-chain attack against LiteLLM within a single year, following the March 2026 TeamPCP campaign. It illustrates a rapidly maturing attacker playbook that targets AI gateway libraries to achieve broad, simultaneous credential theft across cloud, DevOps, and AI toolchains—a pattern that is accelerating as AI-integrated software becomes ubiquitous in enterprise environments.

Critical impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(high)
LMLateral Movement(medium)
C&CCommand & Control(high)
EExfiltration(high)
IImpact(medium)
Read report
KSMBD Zero-Day Alert: Two Unpatched CVSS 9.0 Linux RCE Flaws Exposed on Public Mailing Lists
KSMBD Zero-Day Alert: Two Unpatched CVSS 9.0 Linux RCE Flaws Exposed on Public Mailing Lists

KSMBD Zero-Day Alert: Two Unpatched CVSS 9.0 Linux RCE Flaws Exposed on Public Mailing Lists

In October 2026, Trend Micro's Zero Day Initiative publicly disclosed two critical remote code execution vulnerabilities in the Linux kernel's KSMBD SMB server module, each rated CVSS 9.0, before any mainline kernel patch was available. ZDI-CAN-33774 requires no authentication and affects any Linux server with KSMBD active on port 445, exploiting a race condition in SMB protocol dispatch. ZDI-CAN-33549 targets SMB Direct over RDMA via an integer underflow enabling heap overflow. Neither flaw has received a CVE or upstream fix, leaving exposed systems in a prolonged window of unmitigated risk across enterprise Linux file-serving environments. The premature public disclosure—driven by a policy that AI-discovered bugs are inherently public—highlights a growing tension between responsible disclosure norms and AI-accelerated vulnerability research. With no patch and no CVE assigned, defenders have limited tooling to prioritize or track remediation, increasing the urgency for network-layer controls such as segmentation, egress filtering, and inline IPS to compensate while kernel fixes work through distribution pipelines.

High impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(high)
LMLateral Movement(medium)
C&CCommand & Control(medium)
EExfiltration(medium)
IImpact(medium)
Read report
ThreatsDay October 2026: AI Secrets Leak, PingCAP Source Code Theft, Signal Hang-Up Flaw, Laravel Auth Bypass, and SafePay Ransomware's 600+ Victims
ThreatsDay October 2026: AI Secrets Leak, PingCAP Source Code Theft, Signal Hang-Up Flaw, Laravel Auth Bypass, and SafePay Ransomware's 600+ Victims

ThreatsDay October 2026: AI Secrets Leak, PingCAP Source Code Theft, Signal Hang-Up Flaw, Laravel Auth Bypass, and SafePay Ransomware's 600+ Victims

In the week of October 22, 2026, a sweeping multi-vector threat bulletin exposed simultaneous incidents across credential theft, supply-chain compromise, AI/GenAI abuse, ransomware, and critical vulnerability exploitation. PingCAP confirmed stolen service-account credentials enabled exfiltration of TiDB Cloud source code and customer records between September 9 and October 7, 2026. Zeabur announced shutdown after plaintext-credential abuse exposed 3.2 million environment variable records and 321,810 accounts. SafePay ransomware surpassed 600 victims since 2024 by chaining known edge-device CVEs with lateral movement and data exfiltration. A critical Laravel TokenGuard bypass (CVE-2026-114509, CVSS 9.2), a Signal RingRTC hang-up flaw (CVE-2026-113380, CVSS 9.3), and a NVIDIA AIStore Kubernetes host-takeover flaw (CVE-2026-65162, CVSS 10.0) compounded organizational risk across cloud, messaging, and container infrastructure. These incidents reflect a maturing attacker playbook: stolen credentials unlock supply-chain footholds, unpatched edge-device vulnerabilities feed ransomware pipelines, and AI-layer weaknesses — from biased code generation to prompt-injection via ChatGPT GitHub Connectors — are becoming primary attack surfaces. Regulatory and intelligence pressure is intensifying, with U.S. agencies banning DeepSeek from federal systems and releasing joint rogue-AI containment guidelines, signaling that AI governance is now a frontline security imperative.

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 PHP Engine Flaws Are Being Weaponized Right Now
PHP2Shell: How Two Critical PHP Engine Flaws Are Being Weaponized Right Now
Internet2 weeks ago

PHP2Shell: How Two Critical PHP Engine Flaws Are Being Weaponized Right Now

Two critical remote code execution vulnerabilities in the PHP engine, CVE-2026-109618 and CVE-2026-109619 (collectively dubbed PHP2Shell), are being actively exploited following the premature leak of technical details ahead of PHP's scheduled October 21, 2026 security release. Because the flaws reside in the PHP runtime itself rather than any single application, every web server running an unpatched PHP version is potentially exposed—spanning popular content management systems including WordPress, Drupal, and Joomla. Threat actors are leveraging public proof-of-concept code to deliver web shells, enabling persistent unauthorized access and downstream lateral movement across compromised infrastructure. PHP2Shell represents a new class of engine-level RCE risk that renders application-layer defenses insufficient on their own. With exploit code already circulating and active scanning campaigns underway, the window for undetected initial compromise is extremely narrow, reinforcing the urgency of both emergency patching and network-layer controls capable of detecting and blocking malicious payloads in transit.

Critical impact

Kill Chain

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