Which versions of calvora are malicious?

The following npm versions of calvora are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate calvora if I installed it?

Remove calvora from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

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

If calvora 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 calvora part of a known attack campaign?

Yes — calvora is associated with the GHSA-jwm3-4ffq-hr73, IN-MAL-2026-011068, IN-MAL-2026-011150 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 calvora 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 calvora (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging calvora across your stack and pipelines.

Malicious package

calvoranpm

calvora is a confirmed malicious npm package (MAL-2026-11010) that executes malicious code on install (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in calvora (npm)

MAL-2026-11010

Immediate action

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

npm uninstall calvora

What this malware does

index.mjs auto-invokes a _sync() routine at module import. Under Linux with NODE_ENV!= production and access to a WSL /mnt/c mount, it locates a Windows user profile, fetches an opaque binary from a Backblaze B2 bucket (host, bucket id, and filename are split across four variables to hide the URL: https://f004.backblazeb2.com/file/dp8hbvocjd2fpza/vite-dep.dat), and writes it as vite-native-helper.exe into the user's Windows Startup folder (AppData/Roaming/Microsoft/Windows/Start Menu/Programs/Startup) for execution at next logon. The payload uses cover-story naming (vite-dep.dat, vite-native-helper.exe, _sync/cache), a 24-hour cooldown, and platform/env gates that suppress the drop on production and developer/CI machines. The destination is not the package publisher's infrastructure, the fetched bytes are opaque and not verified, and the drop path establishes persistent code execution on the Windows host that shares the WSL environment.

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

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

d42150b238e61e7ade93da3750393fdd09523b36d5794ed80e57c6a183029a66

3bc3f7e9ef1bbc85d0303406eac1b28cace865d65ab2bbad1104ba2f0adaaa78

2c61b437783c8c83c4d8112858e96019152b17dfbaff029f0a82404957027bd5

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for calvora (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging calvora across your stack and pipelines.
If you installed it — respond
Remove calvora from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If calvora 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 calvora 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. calvora on npm has been identified as a malicious package (versions 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-jwm3-4ffq-hr73IN-MAL-2026-011068IN-MAL-2026-011150

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks calvora-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database