Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

streak-metric-corenpm

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

MAL-2026-12808
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall streak-metric-core

What this malware does

On any require/import of streak-metric-core, top-level code in the main entry reconstructs a URL from String.fromCharCode integer arrays, resolving to https://f004.backblazeb2.com/file/dp8hbvocjd2fpza/service. The package downloads that opaque binary, writes it to ~/.cache/streak-metric/service, chmods it to 0755, and spawns it detached with a randomized delay via spawn(p, [], { detached: true }).unref(). There is no hash or signature verification, the destination is an anonymous Backblaze B2 bucket unrelated to any declared publisher infrastructure, and the URL is reconstructed at runtime specifically to avoid appearing as a plain string. A comment frames the behavior as an 'optional runtime accelerator', but the code executes unconditionally at module load. This grants the package author arbitrary code execution on the installer's host at import time.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

d85f4f43ac36e53cc3254c7e5050d63105543deb781c8884046b7f5443fc3e21

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

    Remove streak-metric-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.

  3. Did it already run?

    If streak-metric-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.

  4. How O3 protects you

    O3 blocks streak-metric-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

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

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Explore

streak-metric-core (npm) malicious package — MAL-2026-12808 | O3 Security