Which versions of cue-mcp are malicious?

The following npm versions of cue-mcp are flagged malicious: 9999.99.99. Treat any of these as compromised.

How do I remediate cue-mcp if I installed it?

cue-mcp 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 cue-mcp — how do I know if it already compromised me?

If cue-mcp 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.

Is cue-mcp part of a known attack campaign?

Yes — cue-mcp is associated with the IN-MAL-2026-007199 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 cue-mcp across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for cue-mcp (version 9999.99.99).

Malicious package

cue-mcpnpm

Advisory published Jun 23, 2026Updated Jun 23, 2026

cue-mcp is a confirmed malicious npm package (MAL-2026-6294) that steals credentials and exfiltrates sensitive data (malicious version 9999.99.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cue-mcp (npm)

MAL-2026-6294

Immediate action

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

npm uninstall cue-mcp

What this malware does

The package's postinstall.js script runs automatically on npm install and collects host identifying data (os.hostname()) along with process environment variables (process.env), then transmits the data over HTTPS. This shape — system-information harvesting at install time and outbound network transmission via the https module — is a classic install-time exfiltration pattern. There is no legitimate purpose served by reading the installer's environment variables and hostname during postinstall for a package of this kind. Environment variables on developer and CI machines routinely contain credentials (NPM_TOKEN, GITHUB_TOKEN, AWS keys, CI secrets), so this beacon constitutes credential exfiltration risk against any system that installs the package.

Malicious versions

1 flagged

9999.99.99

Indicators of compromise (SHA-256)

5dce71f7cd453bd73a138279dd78ebc607d7c4f6b171bd3b76c7f456a6eb907a

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for cue-mcp (version 9999.99.99).
If you installed it — respond
cue-mcp 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 cue-mcp 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. cue-mcp on npm has been identified as a malicious package (version 9999.99.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007199

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks cue-mcp-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