calmoranpm
Advisory published Updated
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)
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
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for calmora (version 1.0.1).
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 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 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.