Which versions of autbank-core are malicious?

The following npm versions of autbank-core are flagged malicious: 99.0.0, 99.0.2. Treat any of these as compromised.

How do I remediate autbank-core if I installed it?

autbank-core is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed autbank-core — how do I know if it already compromised me?

If autbank-core was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is autbank-core part of a known attack campaign?

Yes — autbank-core is associated with the IN-MAL-2026-017936, IN-MAL-2026-017937 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find autbank-core across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for autbank-core (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging autbank-core across your stack and pipelines.

Malicious package

autbank-corenpm

autbank-core is a confirmed malicious npm package (MAL-2026-14059) that steals credentials and exfiltrates sensitive data (malicious versions 99.0.0, 99.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in autbank-core (npm)

MAL-2026-14059

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall autbank-core

What this malware does

On npm install, preinstall.js enumerates process.env for keys matching credential substrings (KEY, SECRET, TOKEN, PASSWORD, AWS, API, CREDENTIAL, AUTH, PRIVATE, NPM, GIT, GITHUB, GITLAB), reads the working directory's.env and package.json, runs git remote -v, and POSTs the collected data via https to a hardcoded webhook.site collector (https://webhook.site/34e76ae9-12e2-4fea-a33a-24f4e1ac5eb2). A companion postinstall.js labeled internally as 'backup exfil' POSTs os.hostname(), os.userInfo().username, and process.cwd() to the same endpoint. Both lifecycle hooks fire automatically on default install, with no relationship to any advertised package functionality.

Malicious versions

2 flagged

99.0.099.0.2

Indicators of compromise (SHA-256)

4ad44010b651e1b239cfbe69c004f11d9227c483ffe55d549368afb4eb394146

8c4077e84d7c02b7a8259ade848e89f9fd07ba0db7fb06bbaaa0c6e75f3e007d

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for autbank-core (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging autbank-core across your stack and pipelines.
If you installed it — respond
autbank-core is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If autbank-core was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks autbank-core before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. autbank-core on npm has been identified as a malicious package (versions 99.0.0, 99.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017936IN-MAL-2026-017937

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks autbank-core-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database