Executive Summary
In June 2026, a sophisticated supply chain attack known as the Hades campaign targeted the Python Package Index (PyPI), compromising 37 malicious wheel artifacts across 19 packages. The attackers utilized Python's .pth files to execute code automatically during interpreter startup, downloading the Bun JavaScript runtime and running an obfuscated JavaScript payload. This payload harvested a wide range of sensitive data, including credentials for GitHub, npm, PyPI, cloud services, and Kubernetes configurations. The stolen data was exfiltrated to public GitHub repositories with descriptions such as "Hades - The End for the Damned." This incident underscores the evolving nature of supply chain attacks, highlighting the need for enhanced security measures in open-source ecosystems. The use of legitimate package features for malicious purposes demonstrates the attackers' increasing sophistication and the critical importance of vigilant package management and code review processes.
Why This Matters Now
The Hades campaign exemplifies the growing threat of supply chain attacks targeting open-source ecosystems, emphasizing the urgent need for developers and organizations to implement robust security practices and monitor dependencies closely.
Attack Path Analysis
The Hades campaign compromised 19 PyPI packages by embedding malicious startup hooks that executed upon installation, leading to the download and execution of an obfuscated JavaScript payload. This payload escalated privileges by installing the Bun JavaScript runtime, enabling further malicious activities. The malware then moved laterally by accessing various developer and CI/CD credentials across multiple platforms. It established command and control by exfiltrating harvested data to public GitHub repositories. The exfiltrated data included sensitive credentials from platforms like GitHub, AWS, and Kubernetes. The impact was a significant compromise of developer systems and CI/CD environments, leading to potential unauthorized access and data breaches.
Kill Chain Progression
Initial Compromise
Description
Malicious PyPI packages were installed, executing startup hooks that triggered the download and execution of an obfuscated JavaScript payload.
MITRE ATT&CK® Techniques
User Execution: Malicious Library
Command and Scripting Interpreter: Python
Supply Chain Compromise: Compromise Software Dependencies and Development Tools
Modify Authentication Process: Credential API Hooking
Application Layer Protocol: Web Protocols
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
PCI DSS 4.0 – Ensure all system components and software are protected from known vulnerabilities
Control ID: 6.2
NYDFS 23 NYCRR 500 – Cybersecurity Policy
Control ID: 500.03
DORA – ICT Risk Management Framework
Control ID: Article 6
CISA ZTMM 2.0 – Supply Chain Risk Management
Control ID: 3.1
NIS2 Directive – Cybersecurity Risk Management Measures
Control ID: Article 21
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Computer Software/Engineering
PyPI supply chain attacks directly compromise Python development workflows, requiring enhanced egress security and threat detection to prevent credential theft from development environments.
Information Technology/IT
IT organizations face high risk from automated malicious package execution, necessitating zero trust segmentation and multicloud visibility to protect development infrastructure and credentials.
Financial Services
Banking systems using Python packages vulnerable to Bun credential stealers, requiring encrypted traffic controls and egress policy enforcement to prevent data exfiltration attacks.
Health Care / Life Sciences
Healthcare development teams exposed to supply chain compromise risk, demanding Kubernetes security and anomaly detection to protect patient data and research systems.
Sources
- Hades PyPI Attack: 19 Packages Poisoned to Auto-Run Bun Credential Stealerhttps://thehackernews.com/2026/06/hades-pypi-attack-19-packages-poisoned.htmlVerified
- Hades Cluster Backdoors 19 PyPI Research Packageshttps://aiweekly.co/alerts/hades-cluster-backdoors-19-pypi-research-packagesVerified
- Miasma Supply Chain Attack Compromises Red Hat npm Packages, Steals Cloud and CI/CD Credentialshttps://blog.actipace.com/news/2026/06/miasma-supply-chain-attack-compromises-red-hat-npm-packages-steals-cloud-and-ci-cd-credentials/Verified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Aviatrix Zero Trust CNSF is pertinent to this incident as it could have limited the attacker's ability to move laterally and exfiltrate data by enforcing strict segmentation and identity-based access controls.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: The attacker's ability to execute unauthorized scripts upon package installation could have been constrained, reducing the risk of initial payload execution.
Control: Zero Trust Segmentation
Mitigation: The attacker's ability to escalate privileges by installing unauthorized runtimes could have been limited, reducing the scope of potential damage.
Control: East-West Traffic Security
Mitigation: The attacker's ability to move laterally and access sensitive credentials across systems could have been constrained, limiting unauthorized access.
Control: Multicloud Visibility & Control
Mitigation: The attacker's ability to establish command and control channels to external repositories could have been limited, reducing unauthorized data transmission.
Control: Egress Security & Policy Enforcement
Mitigation: The attacker's ability to exfiltrate sensitive data to external destinations could have been constrained, limiting data breaches.
The overall impact of unauthorized access and potential data breaches could have been reduced, limiting the blast radius of the attack.
Impact at a Glance
Affected Business Functions
- Software Development
- Continuous Integration/Continuous Deployment (CI/CD)
- Cloud Infrastructure Management
Estimated downtime: 7 days
Estimated loss: $500,000
Exposure of developer credentials, including GitHub tokens, cloud service API keys, and CI/CD secrets.
Recommended Actions
Key Takeaways & Next Steps
- • Implement strict package integrity checks and verify the authenticity of dependencies before installation.
- • Enforce least privilege access controls to limit the impact of potential compromises.
- • Monitor and restrict east-west traffic within the network to detect and prevent lateral movement.
- • Establish robust egress filtering policies to control outbound traffic and prevent unauthorized data exfiltration.
- • Deploy anomaly detection systems to identify and respond to unusual activities indicative of compromise.
