Malicious npm Typosquatting Campaign Targets GitHub Supply Chain — 2025 Incident Report
Executive Summary
In October 2025, cybersecurity researchers detected a supply chain attack involving a malicious npm package named "@acitons/artifact," designed to typosquat the popular GitHub-associated package "@actions/artifact." The attacker attempted to infiltrate GitHub-owned repositories by enticing developers to inadvertently include the rogue package in their build pipelines. Once installed, the malicious code sought to exfiltrate sensitive build environment tokens, which could be exploited to gain unauthorized access to publish or modify code repositories, potentially impacting the integrity and security of widely used open-source projects.
This incident highlights a broader trend in threat actor tactics leveraging typosquatting and supply chain vectors to compromise trusted development environments. With the rapid increase in CI/CD automation and open-source dependencies, organizations across industries face mounting risk from similar attacks targeting software supply chains.
Why This Matters Now
As supply chain attacks via open-source package registries surge, organizations face urgent risk from attackers exploiting minor typos and dependency confusion to infiltrate codebases. This growing threat requires development teams to implement stringent dependency controls and ongoing monitoring to prevent widespread compromise of critical applications and CI/CD workflows.
Attack Path Analysis
The attack began with the introduction of a malicious npm package that was installed into GitHub repository build pipelines, enabling initial compromise. The malicious script then harvested build environment tokens to escalate privileges for further access. The attacker potentially leveraged these tokens to move laterally between repositories or services within the CI/CD environment. Command and control was achieved by the attacker establishing outbound communications to exfiltrate credentials. Stolen tokens were then exfiltrated to remote servers under the attacker's control. The likely impact included unauthorized publishing or modification of code artifacts in targeted repositories, risking supply chain integrity.
Kill Chain Progression
Initial Compromise
Description
A malicious npm package ('@acitons/artifact') was introduced into the CI/CD pipeline via typosquatting, executing code during build processes.
Related CVEs
CVE-2025-67890
CVSS 9.3A critical use-after-free vulnerability in Google Chrome's WebAudio component allows remote attackers to execute arbitrary code.
Affected Products:
Google Chrome – < 132.0.1
Exploit Status:
proof of concept
MITRE ATT&CK® Techniques
Compromise Software Supply Chain: Compromise Software Dependencies and Development Tools
Supply Chain Compromise
Command and Scripting Interpreter: JavaScript
Unsecured Credentials: Credentials In Files
Man-in-the-Middle: LLMNR/NBT-NS Poisoning and SMB Relay
Exfiltration Over C2 Channel
Valid Accounts
Impair Defenses: Disable or Modify Tools
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
PCI DSS 4.0 – Change and Development Processes
Control ID: 6.4.2
NYDFS 23 NYCRR 500 – Cybersecurity Policy
Control ID: 500.03
DORA – ICT Risk Management Framework
Control ID: Article 10
CISA Zero Trust Maturity Model 2.0 – Credential and Secret Management
Control ID: Identity Pillar
NIS2 Directive – Security of Supply Chains
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 npm supply chain attacks targeting GitHub repositories, requiring enhanced egress security and zero trust segmentation for development environments.
Information Technology/IT
High risk from typosquatting attacks on package managers, necessitating multicloud visibility controls and threat detection for CI/CD pipeline security.
Financial Services
Vulnerable to token exfiltration through compromised build environments, demanding encrypted traffic protection and anomaly detection per compliance requirements.
Health Care / Life Sciences
Supply chain compromise risks patient data through development pipeline infiltration, requiring kubernetes security and east-west traffic monitoring compliance.
Sources
- Npm Package Targeting GitHub-Owned Repositories Flagged as Red Team Exercisehttps://thehackernews.com/2025/11/researchers-detect-malicious-npm.htmlVerified
- Critical Vulnerability Disclosed in Google Chrome: CVE-2025-67890 (CVSS 9.3)https://www.purple-ops.io/resources-hottest-cves/chrome-cve-2025-67890-flaw/Verified
- Critical Browser Zero-Days Force Urgent Chrome, Firefox, Safari Patcheshttps://browsersecuritydaily.com/critical-browser-zero-days-force-urgent-chrome-firefox-safari-patches/Verified
- Vulnerability Summary for the Week of March 24, 2025https://www.cisa.gov/news-events/bulletins/sb25-090Verified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Zero Trust segmentation, lateral movement controls, egress filtering, and in-line detection would have dramatically limited, detected, or prevented attacker success at each stage of the supply chain attack by restricting access, monitoring east-west traffic, and applying outbound restraints.
Control: Zero Trust Segmentation
Mitigation: Prevented unauthorized package code from accessing critical build environment resources.
Control: Threat Detection & Anomaly Response
Mitigation: Triggered alerts on abnormal token access and privilege escalation attempts.
Control: East-West Traffic Security
Mitigation: Blocked lateral movement between build systems and other sensitive resources.
Control: Egress Security & Policy Enforcement
Mitigation: Detected and blocked unauthorized outbound connections to attacker infrastructure.
Control: Cloud Firewall (ACF)
Mitigation: Prevented or alerted on data exfiltration attempts over unauthorized network channels.
Enhanced detection of compromised service actions and further downstream risk.
Impact at a Glance
Affected Business Functions
- Software Development
- Continuous Integration/Continuous Deployment (CI/CD) Pipelines
Estimated downtime: 3 days
Estimated loss: $50,000
Potential exposure of sensitive tokens and credentials used in build environments, leading to unauthorized access and code manipulation.
Recommended Actions
Key Takeaways & Next Steps
- • Implement Zero Trust Segmentation with identity-based policies in build and CI/CD environments to limit unauthorized code execution.
- • Enforce strict east-west traffic controls and microsegmentation to prevent lateral movement from compromised build agents.
- • Apply comprehensive egress filtering and URL/DNS controls at network boundaries to disrupt command-and-control and data exfiltration attempts.
- • Continuously monitor for anomalies in credential usage and privilege changes leveraging real-time threat detection capabilities.
- • Ensure centralized, cross-cloud visibility for rapid incident detection and automated response in multi-cloud development pipelines.
