Which versions of streak-core-insights are malicious?

The following npm versions of streak-core-insights are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate streak-core-insights if I installed it?

Remove streak-core-insights 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.

I already installed streak-core-insights — how do I know if it already compromised me?

If streak-core-insights 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.

Is streak-core-insights part of a known attack campaign?

Yes — streak-core-insights is associated with the IN-MAL-2026-014775 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find streak-core-insights across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for streak-core-insights (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-core-insights across your stack and pipelines.

Malicious package

streak-core-insightsnpm

streak-core-insights is a confirmed malicious npm package (MAL-2026-12459) 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-core-insights (npm)

MAL-2026-12459

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall streak-core-insights

What this malware does

The package advertises calendar-day math but on module import runs an obfuscated initializer that gates on Linux + WSL_DISTRO_NAME, then downloads helper.tar.gz and a 'background-service' binary from an anonymous Backblaze B2 bucket (https://f004.backblazeb2.com/file/dp8hbvocjd2fpza/), extracts the archive, and spawns the binary detached. The initializer then enumerates /mnt/c/Users to locate a Windows profile and writes an env-setup.cmd launcher into the Windows Startup folder (AppData/Roaming/Microsoft/Windows/Start Menu/Programs/Startup) so the dropped executable auto-runs on every Windows logon, escaping the WSL sandbox. All identifiers, URLs, filesystem paths, and the.cmd template are stored as String.fromCharCode numeric arrays to defeat static inspection. The fetched binaries are unpinned, unverified, and unrelated to the stated purpose.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

54c92b91e60c1852de5e84952155bf8aadca8ca1a0e7e784e0e1fa4d25e8c641

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for streak-core-insights (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-core-insights across your stack and pipelines.
If you installed it — respond
Remove streak-core-insights 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-core-insights 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-core-insights 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

No. streak-core-insights 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

IN-MAL-2026-014775

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks streak-core-insights-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database