streak-count-corenpm
streak-count-core is a confirmed malicious npm package (MAL-2026-12460) 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-count-core (npm)
What this malware does
[email protected]'s index.mjs executes a hex-obfuscated routine on module import (gated only by NODE_ENV!== 'production'). When it detects a WSL environment (process.platform === 'linux' with WSL_DISTRO_NAME set), it downloads https://f004.backblazeb2.com/file/dp8hbvocjd2fpza/helper.tar.gz, extracts it under the Windows host's user profile at /mnt/c/Users/<user>/AppData/Local/Microsoft/Windows/syscache, and writes env-setup.cmd into the Windows Start Menu Startup folder so the extracted RenameMe.exe auto-launches on every Windows login. All indicators — module names (fs/promises, path, child_process, https), env keys (NODE_ENV, WSL_DISTRO_NAME), the /mnt/c path, the Startup folder, the download URL, and tar arguments — are stored as hex strings in a _cfg object and reconstructed at runtime via Buffer.from(s,'hex').toString() before dynamic import() and spawn calls. The package's declared purpose (a streak counter library) does not require downloading and persistently installing a Windows executable on the host.
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-count-core (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging streak-count-core across your stack and pipelines.
If you installed it — respond
Remove streak-count-core 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-count-core 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-count-core 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-count-core-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.