Malicious code in autbank-core (npm)
The npm package autbank-core contained malicious preinstall and postinstall lifecycle hooks that exfiltrated environment variables, credentials, and system information to a hardcoded webhook.site endpoint during installation.
- Disclosed
- Last updated
- Blast radius
- Any developer or CI/CD system installing autbank-core from npm
- Ecosystems
- Attack vectors
- Affected entities
- autbank-corenpm package
The autbank-core npm package contained malicious code in preinstall.js and postinstall.js lifecycle hooks that executed automatically on npm install. The preinstall.js script enumerated process.env for keys matching credential-related substrings (KEY, SECRET, TOKEN, PASSWORD, AWS, API, CREDENTIAL, AUTH, PRIVATE, NPM, GIT, GITHUB, GITLAB), read the working directory's .env and package.json files, executed git remote -v, and POSTed the collected data to a hardcoded webhook.site collector endpoint (https://webhook.site/34e76ae9-12e2-4fea-a33a-24f4e1ac5eb2).
A companion postinstall.js script labeled internally as 'backup exfil' POSTed additional system information including os.hostname(), os.userInfo().username, and process.cwd() to the same endpoint. Both lifecycle hooks fired automatically on default npm install with no relationship to any advertised package functionality.
The malicious package was identified and credited to the OpenSSF's malicious-packages repository (MAL-2026-14059).
Indicators of compromise
- Packages
- autbank-core
- Domains
- webhook.site
Remediation
- Immediately uninstall autbank-core from all systems and CI/CD pipelines
- Audit npm install logs to identify when the package was installed
- Rotate all credentials, API keys, tokens, and secrets that may have been exposed
- Review git remote configurations and authentication credentials for unauthorized access
- Scan systems for any additional malicious artifacts or persistence mechanisms
- Implement npm package scanning and verification in CI/CD pipelines to detect malicious lifecycle hooks
- Consider using npm audit and tools like Snyk to identify compromised dependencies
Sources
- GitHub Advisory GHSA-96pg-c3cg-m9h7 · GitHub Advisory Database
Cite this entry
"Malicious code in autbank-core (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 15, 2026; last updated August 15, 2026. https://supplychainattack.org/incident/malicious-code-in-autbank-core-npm-18cvyj
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in rust-testing-utils (npm)
The npm package rust-testing-utils contained malicious code that impersonates the pino logger and executes remotely-fetched code with arbitrary privileges. The package spawns a child process that decodes a hardcoded URL, fetches attacker-controlled content, and executes it via Function constructor with full module-loading capability.
npmCompromised packageMalicious commit - containedcritical
Malicious code in stillm4ddpocs-demo-sprocket (npm)
The npm package stillm4ddpocs-demo-sprocket version 999.9.12 contains malicious code that exfiltrates system and project metadata via multiple channels (HTTPS, HTTP, and DNS) to a hardcoded callback host. The package uses a high version number to exploit dependency-confusion attacks against organizations with internal packages of the same name.
npmCompromised packageDependency confusion - containedcritical
Malicious code in @syncraft-labs/react (npm)
The npm package @syncraft-labs/react contained obfuscated malicious code in its ESM distribution that implements the EtherHiding pattern, fetching and executing arbitrary code from an Ethereum smart contract via RPC endpoints. The tampering occurred post-build in the dist/index.js artifact.
npmCompromised package - containedcritical
Malware in hydration-dim-kit
Malware was discovered in the npm package hydration-dim-kit. Any computer with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.
npmCompromised package