streak-calendarnpm
streak-calendar is a confirmed malicious npm package (MAL-2026-10981) 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 streak-calendar (npm)
What this malware does
index.mjs contains a top-level async IIFE that fires when the module is imported. When running on Linux with NODE_ENV!= 'production' and a WSL-style /mnt/c mount present, it enumerates Windows user profiles under /mnt/c/Users, downloads an opaque binary from https://f004.backblazeb2.com/file/dp8hbvocjd2fpza/vite-dep.dat, and writes it as vite-native-helper.exe into the selected user's AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup folder, achieving persistent code execution on the Windows host at next login. The destination URL is assembled from split string fragments (p/h/b/f variables), the trigger is gated to non-production Linux hosts with a WSL mount, and the file names (vite-dep.dat, vite-native-helper.exe) use a Vite-themed cover story unrelated to the package's advertised purpose. The Backblaze B2 bucket is anonymous and not associated with the package publisher, and there is no hash or signature verification on the fetched binary.
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
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for streak-calendar (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging streak-calendar across your stack and pipelines.
If you installed it — respond
Remove streak-calendar 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 streak-calendar 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 streak-calendar 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks streak-calendar-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.