Malicious code in blueai-cli (npm)
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
osv · MAL-2026-16024
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (fa623814be7289a45580d8333138d25b98458b558fbe67c447294944723ec844) 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. ## Source: ghsa-malware (845e864164934025d66335978e97186f1ff11821a8b4d7f5c7948da85e0e7f35) 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.
- Source published
- 7 Sep 2026 13:51:36 UTC
- Source modified
- 8 Sep 2026 20:30:09 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.