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

streak-daycountnpm

Advisory published Updated

streak-daycount is a confirmed malicious npm package (MAL-2026-10982) 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 streak-daycount (npm)

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

What this malware does

[email protected] ships an index.mjs whose top-level async IIFE runs on import. When the host is Linux and NODE_ENV is not 'production', the code enumerates /mnt/c/Users (WSL access to the Windows host filesystem), skips built-in profiles ('Default','Public','All Users'), and identifies real user profiles by the presence of NTUSER.DAT. It then constructs the path AppData/Roaming/Microsoft/Windows/Start Menu/Programs/Startup under that user, downloads a binary from https://f004.backblazeb2.com/file/<bucket>/vite-deps.dat (URL assembled from split fragments p/h/b/f), and writes the bytes as 'vite-native-helper.exe' into the Windows Startup folder — causing the fetched binary to auto-execute on the next Windows logon. The download uses no hash or signature verification, the destination is an anonymous Backblaze B2 bucket unrelated to the package's advertised 'streak day counter' purpose, and the 'vite-native-helper' naming is a decoy referencing an unrelated tool. The bucket identifier is currently a 'YOUR_BUCKET_NAME' placeholder, but the code path is fully wired and activates as soon as it is populated. The Linux+WSL gating specifically targets developer machines that run Node under WSL while backing onto a Windows user profile.

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

Indicators of compromise (SHA-256)

d5a02c91969e01fc57050b8fabfc6abe2e50b9455cdaa4357791d24546b5623a
f787426dd4d04d5cd527bdb19d309c64de82e252af4af0714dc33b07a26b73b0

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for streak-daycount (version 1.0.0).

  2. If you installed it — respond

    Remove streak-daycount 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-daycount 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-daycount 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

GHSA-2v57-6hmf-hpfjIN-MAL-2026-011196

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks streak-daycount-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-daycount (npm) malicious package — MAL-2026-10982 | O3 Security