NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

streak-calendarnpm

Advisory published Updated

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)

MAL-2026-10981
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall streak-calendar

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

2 flagged
1.0.01.0.1

Indicators of compromise (SHA-256)

cdbe692fd3eb07f38adbdf075f40fb7f0f656154e5f2e54570a97d6f6e1bba9a
423bee6d856bd804061bf56f9b8f57f6cbbc0e503ab82c572f539b2f317c30e3
aa3e7016582499a7948d049a47fce7f443692e462107e1a1cd21f2fc7e7c1c4d

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for streak-calendar (2 malicious versions).

  2. 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.

  3. Did it already run?

    If streak-calendar 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

No. streak-calendar 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-2p69-mmpj-h84rIN-MAL-2026-010966IN-MAL-2026-011098

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.

Explore

streak-calendar (npm) malicious package — MAL-2026-10981 | O3 Security