Malicious code in streak-count-core (npm)
The npm package streak-count-core version 1.0.0 contains malicious code that activates when not in production mode and running in a Windows Subsystem for Linux (WSL) environment. It downloads and extracts a Windows executable to the user's profile and configures it to auto-launch on Windows login, despite the package's stated purpose as a streak counter library.
AI Analysis
Technical Summary
The [email protected] package includes a hex-obfuscated routine triggered on module import when NODE_ENV is not 'production' and the environment is detected as WSL. It downloads a helper.tar.gz archive from a remote URL, extracts it into the Windows user's AppData Local path via the WSL mount point, and writes a command script into the Windows Startup folder to ensure persistent execution of RenameMe.exe on every Windows login. The malicious behavior is concealed by storing key strings as hex and reconstructing them at runtime. This behavior is unrelated to the package's declared functionality, indicating intentional malicious code insertion.
Potential Impact
This malicious package can establish persistent malware on Windows hosts running WSL by downloading and installing an executable that auto-launches at user login. This can lead to unauthorized code execution and potential compromise of the affected system. The impact is limited to environments running WSL with NODE_ENV not set to 'production'.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should avoid using streak-count-core version 1.0.0 and remove it from their projects. Since the package performs malicious actions only when NODE_ENV is not 'production' and WSL is detected, setting NODE_ENV to 'production' is a partial mitigation but does not remove the malicious code. Users should audit dependencies for this package and remove any installed instances. Monitor for and delete the downloaded files and startup scripts if present.
Malicious code in streak-count-core (npm)
Description
The npm package streak-count-core version 1.0.0 contains malicious code that activates when not in production mode and running in a Windows Subsystem for Linux (WSL) environment. It downloads and extracts a Windows executable to the user's profile and configures it to auto-launch on Windows login, despite the package's stated purpose as a streak counter library.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The [email protected] package includes a hex-obfuscated routine triggered on module import when NODE_ENV is not 'production' and the environment is detected as WSL. It downloads a helper.tar.gz archive from a remote URL, extracts it into the Windows user's AppData Local path via the WSL mount point, and writes a command script into the Windows Startup folder to ensure persistent execution of RenameMe.exe on every Windows login. The malicious behavior is concealed by storing key strings as hex and reconstructing them at runtime. This behavior is unrelated to the package's declared functionality, indicating intentional malicious code insertion.
Potential Impact
This malicious package can establish persistent malware on Windows hosts running WSL by downloading and installing an executable that auto-launches at user login. This can lead to unauthorized code execution and potential compromise of the affected system. The impact is limited to environments running WSL with NODE_ENV not set to 'production'.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should avoid using streak-count-core version 1.0.0 and remove it from their projects. Since the package performs malicious actions only when NODE_ENV is not 'production' and WSL is detected, setting NODE_ENV to 'production' is a partial mitigation but does not remove the malicious code. Users should audit dependencies for this package and remove any installed instances. Monitor for and delete the downloaded files and startup scripts if present.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-12460
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a735750bf8831d53915a640
Added to database: 08/05/2026, 15:31:28 UTC
Last enriched: 08/05/2026, 15:44:58 UTC
Last updated: 08/05/2026, 15:51:23 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.