blueai-clinpm
Advisory published Updated
blueai-cli is a confirmed malicious npm package (MAL-2026-16024) that steals credentials and exfiltrates sensitive data (malicious version 0.7.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in blueai-cli (npm)
What this malware does
package.json declares "preinstall": "bun run index.js", causing npm install to execute a 499KB obfuscator.io-style file via the Bun runtime. index.js uses hex-mangled identifiers, a rotating string array (_0x71ec), a PBKDF2-derived key with multi-round RC4/XOR string encryption (class du), and installs a decrypt sink on globalThis, alongside an embedded base64 blob. The payload contains GitHub API logic that validates a token against https://api.github.com/user and enumerates organizations via /user/orgs, parsing X-OAuth-Scopes for repo/workflow/public_repo and reading X-GitHub-OAuth-Token-Expiration, returning a {valid, user, scopes, expiry, orgs, hasRepoScope, hasWorkflowScope} structure characteristic of a GitHub personal-access-token harvester. The advertised purpose (a media CLI targeting bluemediagroup.cn endpoints) does not require an obfuscated install-time blob, an alternate runtime, or inspection of installer-owned GitHub credentials; the shipped dist/ tree is unobfuscated, confirming the preinstall file is an evasion-layered install-time execution channel independent of the library.
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
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for blueai-cli (version 0.7.0).
If you installed it — respond
blueai-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.
Did it already run?
If blueai-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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks blueai-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.