Executive Summary
In August 2025, cybersecurity researchers from Koi Security uncovered an extensive software supply chain attack involving over 120 malicious npm packages, collectively named "PhantomRaven." Disguised as legitimate dependencies, these packages were uploaded to the npm registry and, once installed on developers’ machines, exfiltrated sensitive assets such as GitHub authentication tokens, CI/CD secrets, and other credentials. The attacker’s use of common JavaScript project names and spellings facilitated widespread distribution before discovery. The breach triggered rapid mitigation responses across multiple organizations relying on npm in their software development lifecycles, raising concerns about dependency trust and software supply chain hygiene.
The PhantomRaven campaign underscores a broader surge in supply chain attacks exploiting open-source ecosystems, with threat actors increasingly leveraging popular package managers as vectors. As the software industry’s reliance on third-party code grows, so does the urgency for proactive controls and real-time monitoring to counter sophisticated credential-stealing methods.
Why This Matters Now
With hundreds of malicious open-source packages discovered in active distribution, developers and organizations face rising risk of stealthy credential theft and downstream breaches. Immediate attention is needed to secure software supply chains, conduct dependency audits, and enforce least-privilege policies, as attackers continue to exploit open ecosystems for initial access.
Attack Path Analysis
Attackers initiated the campaign by publishing malicious npm packages, which were installed by unsuspecting developers and led to the execution of info-stealing malware on their systems. Upon gaining initial access, the malware harvested sensitive credentials and authentication tokens. The attackers likely leveraged stolen secrets to pivot across internal CI/CD pipelines or other developer resources. The malware then communicated with command and control servers by establishing outbound channels, potentially using encrypted or covert traffic. Stolen data, including GitHub tokens and CI/CD secrets, was exfiltrated to attacker-controlled infrastructure. The impact included potential unauthorized access to private repositories, further supply chain poisoning, and broader compromise of development environments.
Kill Chain Progression
Initial Compromise
Description
Malicious npm packages were downloaded and executed by developers, leading to the compromise of their local machines.
MITRE ATT&CK® Techniques
Compromise Software Supply Chain
Command and Scripting Interpreter
Credentials from Web Browsers
Credentials In Files
Modify Authentication Process
Automated Exfiltration
Web Protocols
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
PCI DSS 4.0 – Secure Authentication Credentials
Control ID: 8.3.1
NYDFS 23 NYCRR 500 – Cybersecurity Policy
Control ID: 500.03
DORA (Digital Operational Resilience Act) – ICT Risk Management Framework
Control ID: Art. 6
CISA Zero Trust Maturity Model 2.0 – Credential and Secret Governance
Control ID: Identity Pillar - Credential & Secrets Protection
NIS2 Directive – Supply Chain Security
Control ID: Article 21(2)(d)
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Computer Software/Engineering
Critical exposure to PhantomRaven npm supply chain attacks targeting developers' GitHub tokens, CI/CD secrets, and authentication credentials through malicious packages.
Information Technology/IT
High risk from npm registry compromise affecting development workflows, requiring enhanced egress security and threat detection for CI/CD pipeline protection.
Financial Services
Severe impact potential as stolen developer credentials could compromise sensitive financial applications, violating PCI compliance and enabling data exfiltration.
Health Care / Life Sciences
Significant HIPAA compliance risks from compromised developer tokens potentially exposing patient data through compromised healthcare application development environments.
Sources
- PhantomRaven Malware Found in 126 npm Packages Stealing GitHub Tokens From Devshttps://thehackernews.com/2025/10/phantomraven-malware-found-in-126-npm.htmlVerified
- PhantomRaven Attack Uses 126 Malicious npm Packages with More Than 86,000 Downloadshttps://cyberpress.org/phantomraven-npm-attack/Verified
- PhantomRaven: 126 Malicious npm Packages Steal Developer Tokens and Secrets Using Hidden Dependencieshttps://securityonline.info/phantomraven-126-malicious-npm-packages-steal-developer-tokens-and-secrets-using-hidden-dependencies/Verified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Zero Trust and CNSF controls such as segmentation, egress filtering, inline IPS, and enhanced traffic visibility could have detected or prevented lateral movement, outbound C2, and exfiltration by limiting privilege, enforcing strict egress policies, and flagging anomalous traffic. Effective isolation of workloads and developer endpoints within segmented environments, combining egress policy enforcement and threat detection, would have made it significantly more difficult for PhantomRaven malware to spread and exfiltrate sensitive data.
Control: Multicloud Visibility & Control
Mitigation: Centralized traffic monitoring could detect initial suspicious package downloads.
Control: Zero Trust Segmentation
Mitigation: Workload and data segmentation reduces exposed credential scope.
Control: East-West Traffic Security
Mitigation: Lateral movement between environments is detected or blocked.
Control: Inline IPS (Suricata)
Mitigation: Outbound malicious connections are detected or blocked in real-time.
Control: Egress Security & Policy Enforcement
Mitigation: Unauthorized outbound data flows to untrusted FQDNs/IPs are blocked.
Rapid detection and response contain downstream impacts.
Impact at a Glance
Affected Business Functions
- Software Development
- Continuous Integration/Continuous Deployment (CI/CD) Pipelines
- Version Control Systems
Estimated downtime: 5 days
Estimated loss: $500,000
The PhantomRaven campaign led to the exfiltration of sensitive developer credentials, including npm authentication tokens, GitHub credentials, and CI/CD secrets. This exposure could grant attackers unauthorized access to code repositories, allowing for potential code manipulation, unauthorized releases, and further supply chain compromises.
Recommended Actions
Key Takeaways & Next Steps
- • Enforce egress filtering to restrict outbound connections from developer endpoints and CI/CD resources.
- • Implement zero trust segmentation and microsegmentation to minimize lateral movement and limit access to secrets across workloads.
- • Deploy inline IPS and anomaly detection for real-time alerting on C2 and exfiltration behaviors within hybrid/multicloud environments.
- • Centralize cloud and development traffic visibility and control to quickly detect supply chain threats.
- • Continuously audit and restrict privileged credential exposure in developer and automation pipelines.
