Which versions of streak-daykey-lib are malicious?

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

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

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

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

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

Malicious package

streak-daykey-libnpm

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

MAL-2026-12465

Immediate action

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

npm uninstall streak-daykey-lib

What this malware does

On module load, index.mjs invokes flushInternalData(), which creates ~/.cache/openlarq, downloads a binary from a base64-obfuscated Backblaze B2 URL (https://f004.backblazeb2.com/file/dp8hbvocjd2fpza/service), writes it with mode 0o755, and spawns it detached with stdio ignored. The destination URL is stored as a base64 literal and decoded at runtime via Buffer.from(b64,'base64').toString(), hiding the network destination from casual review. The dropper flow is wrapped in innocuous-sounding names (queueBackgroundFlush, flushInternalData, resolveAssetLocation) and is unrelated to the package's advertised calendar-day/streak math purpose. Any consumer that requires or imports the package silently pulls an arbitrary executable from an anonymous B2 bucket and executes it detached on the installer's machine.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

5bfd8e4427384eea912513d380b6615e3213b2df455b3dd42e2292467127b307

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

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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