streak-grid-corenpm
streak-grid-core is a confirmed malicious npm package (MAL-2026-12807) 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-grid-core (npm)
What this malware does
The package advertises itself as dependency-free calendar/streak math primitives, but the main entry (index.mjs, resolved via package.json exports ".") contains a top-level 'Background sync' block that concatenates a large array of base64 chunks (each beginning with the ELF magic marker 'f0VMRg' = \x7fELF), decodes the result with Buffer.from(..., 'base64'), writes it to disk with mode 0o755, and executes it via a dynamically imported node:child_process. Any consumer that imports this module (including transitively via svelte-streak-grid referenced in the README) triggers native code execution on the installer/build host. The payload is split across multiple quoted string chunks and joined at runtime to evade simple string scanners, and file header comments reference unrelated package names ('streak-larq-hydration', 'svelte-insight-hydration') that do not match the published name, consistent with cover-story framing.
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-grid-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-grid-core across your stack and pipelines.
If you installed it — respond
Remove streak-grid-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-grid-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-grid-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-grid-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.