Malicious code in streak-core-lib (npm)
streak-core-lib@1.0.0 on npm contains malicious code that drops a Windows PE executable to the Startup folder on installation, achieving persistent code execution. The package falsely advertises itself as a day-math primitives library and executes the payload automatically on import without user interaction.
- Disclosed
- Last updated
- Blast radius
- Windows hosts that installed streak-core-lib@1.0.0
- Ecosystems
- Attack vectors
- Affected entities
- streak-core-lib · 1.0.0
streak-core-lib@1.0.0 is a malicious npm package that masquerades as a 'day-math primitives' library. The package's index.mjs file contains an end-of-file async IIFE that decodes a hex-encoded Windows PE binary and writes it to the user's Startup folder as vite-native-helper.exe (%AppData%/Roaming/Microsoft/Windows/Start Menu/Programs/Startup/vite-native-helper.exe).
The malicious payload is obfuscated using hex-literal arrays that are decoded at runtime to hide the file paths and executable name from static analysis. The embedded binary begins with the MZ header (4D5A90) characteristic of Windows PE executables. Files placed in the Windows Startup folder execute automatically at every user logon, providing persistent code execution on the affected system.
The package contains inline comments falsely claiming it 'touches no network and no filesystem' and requires 'no npm lifecycle script', directly contradicting the fs.writeFile call that drops the executable. The malicious behavior is triggered automatically on import without any user interaction beyond package installation.
The incident was identified by the OpenSSF malicious-packages project and reported via GitHub Advisory GHSA-7vpc-qq63-xvwj.
Indicators of compromise
- Packages
- streak-core-lib@1.0.0
Remediation
- Immediately uninstall streak-core-lib from all systems
- Remove vite-native-helper.exe from %AppData%/Roaming/Microsoft/Windows/Start Menu/Programs/Startup/ on affected Windows hosts
- Scan affected systems for the dropped executable and any related malware
- Review npm package dependencies to ensure no other malicious packages are present
- Implement package verification and scanning in the npm supply chain workflow
Sources
- GitHub Advisory GHSA-7vpc-qq63-xvwj · GitHub Advisory Database
Cite this entry
"Malicious code in streak-core-lib (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 28, 2026; last updated July 28, 2026. https://supplychainattack.org/incident/malicious-code-in-streak-core-lib-npm-1jlvx8
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- activecritical
Malware in @omniwatch-wick/cli
Malware discovered in the npm package @omniwatch-wick/cli. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package - activecritical
Malware in chain-manager
Malware discovered in the npm package chain-manager. Systems with this package installed or running are considered fully compromised and require immediate remediation.
npmCompromised package - containedcritical
Malicious code in toll_free (npm)
The npm package toll_free version 1.0.1 was identified as malicious by the OpenSSF Package Analysis project. The package executes commands associated with malicious behavior.
npmCompromised package - containedcritical
Malicious code in blots (npm)
The npm package 'blots' version 2.1.0 was identified by the OpenSSF Package Analysis project as containing malicious code that executes commands associated with malicious behavior. The package has been flagged in the OpenSSF malicious packages database.
npmCompromised package