calvuepronpm
Advisory published Updated
calvuepro is a confirmed malicious npm package (MAL-2026-7028) that steals credentials and exfiltrates sensitive data (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in calvuepro (npm)
What this malware does
Package ships a 5.7MB prebuilt darwin-arm64 Mach-O at vendor/clavuepro-darwin-arm64 with no source tree, no hash/signature verification, and no upstream release URL to cross-reference. The bin wrapper bin/calvuepro.js chmods the binary 0755 and spawns it with the caller's argv via spawnSync. There are no lifecycle scripts and no main field, so the binary executes only when a user explicitly runs the CLI — not on npm install or require(). Notable inconsistency: the npm package name is calvuepro while the shipped binary, repository (mycode699/clavue-v2), and CLI alias all use clavuepro — a one-character difference that is worth a human review of publisher identity before trusting lifecycle execution of opaque native code. No exfiltration, no credential access, no install-time fetch+execute, and no network behavior was observed in the loader script.
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 calvuepro (version 0.1.0).
If you installed it — respond
calvuepro 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 calvuepro 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 calvuepro-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.