Which versions of calvuepro are malicious?

The following npm versions of calvuepro are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate calvuepro if I installed it?

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.

I already installed calvuepro — how do I know if it already compromised me?

If calvuepro was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is calvuepro part of a known attack campaign?

Yes — calvuepro is associated with the GHSA-82qq-fgw6-6hf8, IN-MAL-2026-009426 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 calvuepro across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for calvuepro (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging calvuepro across your stack and pipelines.

Malicious package

calvuepronpm

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)

MAL-2026-7028

Immediate action

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

npm uninstall calvuepro

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

1 flagged

0.1.0

Indicators of compromise (SHA-256)

36e6f293ca556e3d3fdc61b38b76cbbbc74acabcd9dee4ccd35849747f183ff5

9de2057a076c31ca107db2c3e8d330a7b4aa2d8d67896cecd6c7ebef21d07731

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for calvuepro (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging calvuepro across your stack and pipelines.
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 ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks calvuepro before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. calvuepro on npm has been identified as a malicious package (version 0.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-82qq-fgw6-6hf8IN-MAL-2026-009426

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database