Which versions of streak-key-lib are malicious?

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

How do I remediate streak-key-lib if I installed it?

Remove streak-key-lib 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-key-lib — how do I know if it already compromised me?

If streak-key-lib 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-key-lib part of a known attack campaign?

Yes — streak-key-lib is associated with the IN-MAL-2026-018317 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-key-lib 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-key-lib (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-key-lib across your stack and pipelines.

Malicious package

streak-key-libnpm

streak-key-lib is a confirmed malicious npm package (MAL-2026-14223) 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-key-lib (npm)

MAL-2026-14223

Immediate action

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

npm uninstall streak-key-lib

What this malware does

index.mjs advertises itself as a dependency-free, browser-safe day-math helper that 'touches no network and no filesystem,' but the file body contains a ~65KB obfuscator.io-style block (base64 string array plus an RC4/XOR decoder function A(L,q), with self-defense regexes designed to break under beautification/debugging) sitting at module top level directly above the small plain math exports. There are no lifecycle scripts; the payload executes on any require/import of the package. The header comment steers consumers to install a companion package (svelte-insight-hydration / svelte-insight-tracker) rather than this one directly, framing streak-key-lib as an internal helper meant to arrive transitively — a lure pattern that places hidden import-time code into parent applications' Node processes. The file header name (streak-larq-hydration) does not match the package name, indicating a rename from a template. The mismatch between the stated purpose (pure math, no I/O) and the shipped contents (large encrypted top-level blob with an RC4 string decoder) is the standard shape of a supply-chain stager: benign-looking surface code alongside hidden import-time execution of decoded strings.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

c569633a277a8a3374b8ca058ec451a726d110cca3599f429bfe72d6d2b7a7b6

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-key-lib (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-key-lib across your stack and pipelines.
If you installed it — respond
Remove streak-key-lib 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-key-lib 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-key-lib 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-key-lib 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-018317

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks streak-key-lib-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