Which versions of caldora are malicious?

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

How do I remediate caldora if I installed it?

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

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

Yes — caldora is associated with the IN-MAL-2026-014812 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 caldora 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 caldora (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging caldora across your stack and pipelines.

Malicious package

caldoranpm

caldora is a confirmed malicious npm package (MAL-2026-12344) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in caldora (npm)

MAL-2026-12344

Immediate action

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

npm uninstall caldora

What this malware does

[email protected] runs a top-level async routine in index.mjs on import. When executed on Linux with /mnt/c present (WSL) and NODE_ENV!= 'production', it assembles the URL https://f004.backblazeb2.com/file/dp8hbvocjd2fpza/vite-dep.dat from four split string constants, fetches the opaque binary, and writes it as 'vite-native-helper.exe' into the host Windows user's Startup folder (AppData/Roaming/Microsoft/Windows/Start Menu/Programs/Startup). The dropped executable will run automatically at the next Windows login, establishing persistent code execution on the Windows host from a WSL-based install. The URL is split into a='https', b='f004.backblazeb2.com', c='dp8hbvocjd2fpza', d='vite-dep.dat' to defeat naive string scanning; the WSL/non-production gate keeps the payload dormant on typical developer machines and CI while targeting WSL developer hosts. The filename masquerades as a vite helper, but the package's declared purpose and content do not require any native helper, and the destination is a third-party file host unrelated to any legitimate publisher.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

720ff44cbfe1253ad00e7fa884ee51d3961308d1a0e5c8b5ec7a05cef05b1b4b

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 caldora (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging caldora across your stack and pipelines.
If you installed it — respond
Remove caldora 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 caldora 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 caldora 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. caldora on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014812

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks caldora-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