Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

bmc-i18n-extract-clinpm

Advisory published Updated

bmc-i18n-extract-cli is a confirmed malicious npm package (MAL-2026-16025) that steals credentials and exfiltrates sensitive data (malicious version 1.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bmc-i18n-extract-cli (npm)

MAL-2026-16025
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall bmc-i18n-extract-cli

What this malware does

The package's package.json declares a preinstall hook bun run index.js and lists the Bun runtime (bun ^1.3.13) as a dependency, causing an obfuscated ~500KB index.js to execute automatically on npm install under a non-Node runtime. index.js is packed with obfuscator.io (rotated string array _0x71ec) and additionally implements a custom PBKDF2/HMAC-derived cipher whose decrypt function is installed on globalThis; the fetch base URL and User-Agent are reconstructed at runtime from encoded string-array indices rather than appearing as plaintext literals. The payload calls the GitHub API with an Authorization Bearer token, inspects the X-OAuth-Scopes response header for repo and workflow scopes, and enumerates /user/orgs — token triage and org enumeration unrelated to the package's stated i18n/translation purpose. index.js is not listed in package.json's declared files array (bin, dist, types, README.md) yet ships at the tarball root and is referenced by the preinstall script, indicating the payload sits outside the author's declared publish surface.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged
1.1.1

Indicators of compromise (SHA-256)

6567fe3822e10873e7be53d7b830f525aa2fc5efc3083c0fe2b713bd896220eb
70d52b44b46819aa61ff57d4863315b09f655a4fb5b5787843c2a24f85d9c6db

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for bmc-i18n-extract-cli (version 1.1.1).

  2. If you installed it — respond

    bmc-i18n-extract-cli 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.

  3. Did it already run?

    If bmc-i18n-extract-cli was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. bmc-i18n-extract-cli on npm has been identified as a malicious package (version 1.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-327g-rcr8-hp3pIN-MAL-2026-019713

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Explore

bmc-i18n-extract-cli (npm) malicious package — MAL-2026-16025 | O3 Security