[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$feiyfRw6MU1TdKAjnamrD9Y4_zFibU586H3Ee2Aa3Zgc":3},{"article":4,"iocs":50,"watch_terms":61,"solutions":62,"lesson":150},{"id":5,"title":6,"slug":7,"summary":8,"ai_summary":9,"brief":10,"url":11,"image_url":12,"published_at":13,"ingested_at":14,"relevance_score":15,"entities":16,"category_id":30,"category":31,"article_tags":34},"d59bdcff-22dc-428e-8576-eada76294f17","​​Supply Chain Compromise Impacts Axios Node Package Manager​","supply-chain-compromise-impacts-axios-node-package-manager-786b95","The Cybersecurity and Infrastructure Security Agency (CISA) is releasing this alert to provide guidance in response to the software supply chain compromise of the Axios node package manager (npm).1 Axios is an HTTP client for JavaScript that developers commonly use in Node.js and browser environments. On March 31, 2026, two npm packages for versions axios@1.14.1 and axios@0.30.4 of Axios npm injected the malicious dependency plain-crypto-js@4.2.1 that downloads multi-stage payloads from cyber threat actor infrastructure, including a remote access trojan.2 CISA urges organizations to implement the following recommendations to detect and remediate a potential compromise: Monitor and review code repositories, continuous integration\u002Fcontinuous delivery (CI\u002FCD) pipelines, and developer machines that ran npm install or npm update with the compromised Axios version. Search for cached versions of affected dependencies in artifact repositories and dependency management tools. Pin npm package dependency versions to known safe releases. If compromised dependencies are identified, revert the environment to a known safe state. Downgrade to axios@1.14.0 or axios@0.30.3 and delete node_modules\u002Fplain-crypto-js\u002F. Rotate\u002Frevoke credentials that may have been exposed on affected systems or pipelines (e.g., version control system [VCS] tokens, CI\u002FCD secrets, cloud keys, npm tokens, and Secure Shell [SSH] keys). For ephemeral CI jobs, rotate all secrets injected into the compromised run. Monitor for unexpected child processes and anomalous network behavior, specifically during npm install or npm update. Block and monitor outbound connections to Sfrclak[.]com domains. Conduct continuous indicator searches and endpoint detection and response (EDR) hunts to confirm no indicators of compromise (IOCs) remain; ensure no further egress to the command and control (C2). In addition, CISA recommends organizations using Axios npm: Mandate phishing-resistant multifactor authentication (MFA) on all developer accounts, especially for critical platforms. Set ignore-scripts=true in the .npmrc configuration file, which prevents potentially malicious scripts from executing during npm install packages. Set min-release-age=7 in the .npmrc configuration file to only install packages that have been published for at least seven days, which helps avoid installation of packages that may not be completely vetted or are potentially malicious. Establish and maintain a baseline of normal execution behavior for tools that use Axios. Alert when a dependency behaves differently (e.g., building containers, enabling shells, executing commands) and trace outbound network activity for anomalous connections. See the following resources for additional guidance on this compromise: GitHub: Post Mortem: axios npm supply chain compromise #10636 Microsoft: Mitigating the Axios npm supply chain compromise StepSecurity: axios Compromised on npm - Malicious Versions Drop Remote Access Trojan npm Docs: Securing your code Socket: Supply Chain Attack on Axios Pulls Malicious Dependency from npm Disclaimer The information in this report is being provided “as is” for informational purposes only. CISA does not endorse any commercial entity, product, company, or service, including any entities, products, or services linked within this document. Any reference to specific commercial entities, products, processes, or services by service mark, trademark, manufacturer, or otherwise, does not constitute or imply endorsement, recommendation, or favoring by CISA. Notes 1 “Post Mortem: axios npm supply chain compromise,” axios GitHub, Issue #10636, March 31, 2026, https:\u002F\u002Fgithub.com\u002Faxios\u002Faxios\u002Fissues\u002F10636. 2 “Mitigating the Axios npm supply chain compromise,” Microsoft Threat Intelligence and Microsoft Defender Security Research Team, April 1, 2026, https:\u002F\u002Fwww.microsoft.com\u002Fen-us\u002Fsecurity\u002Fblog\u002F2026\u002F04\u002F01\u002Fmitigating-the-axios-npm-supply-chain-compromise\u002F.","On March 31, 2026, two versions of the Axios npm package (axios@1.14.1 and axios@0.30.4) were compromised with a malicious dependency plain-crypto-js@4.2.1 that downloads multi-stage payloads including a remote access trojan from attacker infrastructure. CISA released guidance urging organizations to downgrade affected versions, rotate credentials, monitor for C2 connections to Sfrclak[.]com, and implement preventive measures such as MFA, script execution restrictions, and minimum release-age policies. The compromise affects JavaScript developers across Node.js and browser environments who installed the tainted packages.","Axios npm packages compromised with malicious dependency delivering remote access trojan.","https:\u002F\u002Fwww.cisa.gov\u002Fnews-events\u002Falerts\u002F2026\u002F04\u002F20\u002Fsupply-chain-compromise-impacts-axios-node-package-manager",null,"2026-04-20T12:00:00+00:00","2026-04-20T20:00:07.882398+00:00",9,[17,20,23,25,28],{"name":18,"type":19},"Axios","product",{"name":21,"type":22},"npm","technology",{"name":24,"type":19},"Node.js",{"name":26,"type":27},"CISA","vendor",{"name":29,"type":27},"Microsoft","26b0b636-0e31-4db1-bffb-61bdf9f20a58",{"id":30,"icon":12,"name":32,"slug":33},"Supply Chain","supply-chain",[35,40,45],{"category":36},{"id":37,"icon":12,"name":38,"slug":39},"89f78b1c-3503-45a1-9fc7-e23d2ce1c6d5","Malware","malware",{"category":41},{"id":42,"icon":12,"name":43,"slug":44},"ade75414-7914-4e23-a450-48b64546ee70","Open Source","open-source",{"category":46},{"id":47,"icon":12,"name":48,"slug":49},"e7b231c8-5f79-4465-8d38-1ef13aea5a14","Threat Intelligence","threat-intelligence",[51,55,58],{"type":52,"value":53,"context":54},"domain","Sfrclak[.]com","C2 infrastructure used by threat actor to deliver multi-stage payloads and remote access trojan",{"type":39,"value":56,"context":57},"plain-crypto-js@4.2.1","Malicious npm dependency injected into Axios packages; downloads RAT payloads",{"type":39,"value":59,"context":60},"remote access trojan","Multi-stage payload delivered via compromised Axios dependency",[29,26,18],{"controls":63,"vendors":149},[64,93,122],{"slug":65,"name":66,"problem":67,"products":68},"secrets-management","Secrets management","API keys, tokens and passwords stop leaking from code, chat and configuration files.",[69,77,85],{"vendor_slug":70,"vendor_name":71,"vendor_logo":72,"product_slug":73,"product_name":74,"url":75,"description":76},"gitguardian","GitGuardian","\u002Fvendor-logos\u002Fgitguardian.png","gitguardian-platform","GitGuardian Secrets Detection","https:\u002F\u002Fwww.gitguardian.com\u002F","Finds and helps remediate secrets leaked in repositories, CI pipelines and chat tools.",{"vendor_slug":78,"vendor_name":79,"vendor_logo":80,"product_slug":81,"product_name":82,"url":83,"description":84},"hashicorp","HashiCorp","\u002Fvendor-logos\u002Fhashicorp.png","vault","HashiCorp Vault","https:\u002F\u002Fwww.hashicorp.com\u002Fen\u002Fproducts\u002Fvault","Secrets management with short-lived credentials and encryption as a service.",{"vendor_slug":86,"vendor_name":87,"vendor_logo":88,"product_slug":89,"product_name":90,"url":91,"description":92},"palo-alto-networks","Palo Alto Networks","\u002Fvendor-logos\u002Fpalo-alto-networks.png","idira-secrets-management","Idira Secrets Management","https:\u002F\u002Fwww.paloaltonetworks.com\u002Fidira\u002Fmachine\u002Fsecrets-management","Secrets management for applications, scripts and pipelines, from the former CyberArk portfolio.",{"slug":94,"name":95,"problem":96,"products":97},"endpoint-detection-response","Endpoint detection and response (EDR and XDR)","Malware and hands-on-keyboard attackers on laptops and servers get spotted and stopped.",[98,106,114],{"vendor_slug":99,"vendor_name":100,"vendor_logo":101,"product_slug":102,"product_name":103,"url":104,"description":105},"eset","ESET","\u002Fvendor-logos\u002Feset.png","eset-protect","ESET PROTECT","https:\u002F\u002Fwww.eset.com\u002Fint\u002Fbusiness\u002Fsolutions\u002Fendpoint-protection\u002F","Endpoint protection platform with detection and response add-ons.",{"vendor_slug":107,"vendor_name":108,"vendor_logo":109,"product_slug":110,"product_name":111,"url":112,"description":113},"huntress","Huntress","\u002Fvendor-logos\u002Fhuntress.png","managed-edr","Huntress Managed EDR","https:\u002F\u002Fwww.huntress.com\u002Fplatform\u002Fmanaged-edr","Endpoint detection and response monitored around the clock by Huntress analysts.",{"vendor_slug":115,"vendor_name":116,"vendor_logo":117,"product_slug":118,"product_name":119,"url":120,"description":121},"sentinelone","SentinelOne","\u002Fvendor-logos\u002Fsentinelone.png","singularity-endpoint","Singularity Endpoint","https:\u002F\u002Fwww.sentinelone.com\u002Fplatform\u002Fendpoint-security\u002F","Endpoint protection and detection with automated response and rollback.",{"slug":123,"name":124,"problem":125,"products":126},"software-supply-chain","Software supply chain security","Malicious and vulnerable open-source packages are caught before they ship.",[127,135,141],{"vendor_slug":128,"vendor_name":129,"vendor_logo":130,"product_slug":131,"product_name":132,"url":133,"description":134},"jfrog","JFrog","\u002Fvendor-logos\u002Fjfrog.png","jfrog-curation","JFrog Curation","https:\u002F\u002Fjfrog.com\u002Fcuration\u002F","Blocks malicious and risky open-source packages before they enter your repositories.",{"vendor_slug":136,"vendor_name":137,"vendor_logo":138,"product_slug":136,"product_name":137,"url":139,"description":140},"socket","Socket","\u002Fvendor-logos\u002Fsocket.png","https:\u002F\u002Fsocket.dev\u002F","Detects and blocks malicious and risky packages in npm, PyPI and other ecosystems.",{"vendor_slug":142,"vendor_name":143,"vendor_logo":144,"product_slug":145,"product_name":146,"url":147,"description":148},"github","GitHub","\u002Fvendor-logos\u002Fgithub.png","advanced-security","GitHub Advanced Security","https:\u002F\u002Fgithub.com\u002Fsecurity\u002Fadvanced-security","Dependency review, code scanning and secret scanning with push protection.",[],{"slug":151,"title":152,"body":153,"framework_refs":154,"framework_notes":161},"malicious-dependencies-compromise-popular-axios-npm-package","Malicious Dependencies Compromise Popular Axios npm Package","Attackers successfully injected malicious code into two versions of the widely-used Axios npm package by introducing a compromised dependency (plain-crypto-js@4.2.1) that delivered remote access trojans to developers' systems. This supply chain attack demonstrates how a single compromised package can impact thousands of JavaScript applications across Node.js and browser environments. The incident highlights the critical need for package verification, dependency monitoring, and secure development practices. Organizations must treat third-party dependencies as potential attack vectors and implement controls to detect and prevent malicious code injection.",[155,156,157,158,159,160],"CIS Control 2.1","CIS Control 2.2","NIST SP 800-161","NIST Cybersecurity Framework PR.DS-6","OWASP SCVS","SLSA Framework",{"OWASP SCVS":162,"SLSA Framework":163,"CIS Control 2.1":164,"CIS Control 2.2":165,"NIST SP 800-161":166,"NIST Cybersecurity Framework PR.DS-6":167},"Software component verification covers checking dependencies before trusting them.","Build provenance helps verify that packages come from expected sources.","A software inventory, including dependencies, shows which projects pulled the compromised Axios versions.","Ensuring only authorised software runs helps block the malicious plain-crypto-js dependency.","Supply chain risk management covers vetting dependencies like those added to Axios.","Integrity checking, such as lockfiles and checksums, helps detect unexpected dependency changes."]