BGD e-GOV CIRT published an advisory on 1 April 2026 about a software supply-chain compromise of the widely used Axios JavaScript HTTP client in the npm ecosystem, associated with CVE-2026-32746. CIRT said attackers gained unauthorised access to an npm maintainer account and published malicious versions of Axios containing a remote-access trojan capable of affecting Windows, Linux and macOS. Security researchers, as cited, described a custom cross-platform RAT embedded in a malicious dependency named plain-crypto-js.
Axios, CIRT noted, has millions of weekly downloads and is used in web applications, APIs and development environments, creating risk for developer systems, CI/CD pipelines and production. Although the malicious versions were removed shortly after discovery, systems that installed the compromised packages during the exposure window may already have been infected. CIRT said organisations in Bangladesh using Node.js may be at risk because many local companies use Express, NestJS and Next.js, software teams frequently use npm, and cloud and fintech systems rely on JavaScript API integrations.
The attack chain, as analysed by CIRT, was maintainer-account compromise; publication of axios@1.14.1 and axios@0.30.4; addition of a hidden dependency plain-crypto-js@4.2.1; automatic execution of a post-install script during npm install; download of platform-specific payloads for Windows, macOS and Linux; and command-and-control communication to exfiltrate credentials. Once installed, CIRT said, the malware can steal credentials, SSH keys, .env secrets and Kubernetes tokens and establish remote command execution. Targeted secrets included AWS, Azure and GCP credentials, Kubernetes tokens, SSH private keys, cryptocurrency wallet files and shell history. Those credentials could enable attackers to pivot into enterprise infrastructure or cloud environments. The malicious versions were available on the npm registry for approximately two to three hours.
CIRT recommended checking installed packages with npm list axios and searching lock files, removing malicious versions, and reinstalling axios@1.14.0 or axios@0.30.3. If node_modules/plain-crypto-js is present, treat the system as potentially compromised. Endpoint hunting should look for executables created in /tmp or %PROGRAMDATA%, unexpected Python or shell execution during dependency installation, and suspicious modifications in node_modules. Credentials associated with affected build systems should be rotated. CIRT pointed readers to public analyses by Snyk, Aikido, Elastic Security Labs and Huntress that described the same maintainer-account hijack. Longer-term recommendations included software composition analysis, dependency version pinning, private package registries, CI/CD monitoring of dependency changes, and a software bill of materials.
What this means for organisations in Bangladesh: Banks, MFS providers, software houses and government digital-service teams that run Node.js pipelines should audit lockfiles for the two malicious Axios versions and for plain-crypto-js, treat any hit as a possible developer-workstation compromise, and rotate cloud keys issued from those machines. Report suspected supply-chain infections to CIRT at cirt.gov.bd/report-incident, cti@cirt.gov.bd or info@cirt.gov.bd.
Primary source: BGD e-GOV CIRT advisory “Axios NPM Package Compromise Deploying RAT Affecting Node.js Environments”, 1 April 2026.
Sources
- BGD e-GOV CIRT — Axios NPM Package Compromise Deploying RAT Affecting Node.js Environments2026-09-24
Cyber71 links the primary material behind each report so readers can check it directly. External pages are not under our control and may change.
