Which versions of calmora are malicious?

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

How do I remediate calmora if I installed it?

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

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

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

Malicious package

calmoranpm

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

Malicious code in calmora (npm)

MAL-2026-11009

Immediate action

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

npm uninstall calmora

What this malware does

On import of the package's main entry, a top-level IIFE gated to Linux hosts detects a WSL environment by probing /mnt/c, locates the Windows user profile via NTUSER.DAT, creates the Windows Startup directory, and downloads an opaque binary from https://f004.backblazeb2.com/file/dp8hbvocjd2fpza/vite-dep.dat, writing it as vite-native-helper.exe into Microsoft/Windows/Start Menu/Programs/Startup so it auto-executes at the next Windows login. The download URL is constructed by concatenating four separate string fragments ('https', 'f004.backblazeb2.com', 'dp8hbvocjd2fpza', 'vite-dep.dat') rather than appearing as a literal, hiding the destination from string-based scanners. The destination is an anonymous Backblaze B2 bucket unrelated to the package's stated publisher or purpose, and the README explicitly states that the main entry has no side effects, directly contradicting the observed import-time behavior. The dropped filename ('vite-native-helper.exe') is a cover-story masquerading as Vite tooling.

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

1.0.1

Indicators of compromise (SHA-256)

dd65d988f18a0f4c26e80ba1051269692e38e3461369a9cc62a0314755b06aee

e18af070089392b367436cc347aa8b436273c45c3a1f793232788f844505d63e

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

Campaign

GHSA-7wwx-476f-c8gmIN-MAL-2026-011070

References

Credits

Amazon Inspector · finder

Detect & block this

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