Which versions of streak-daykit are malicious?

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

How do I remediate streak-daykit if I installed it?

streak-daykit is a typosquat — you almost certainly intended a legitimately-named package. Remove streak-daykit, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

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

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

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

Malicious package

streak-daykitnpm

streak-daykit is a confirmed malicious npm package (MAL-2026-12466) that typosquats a legitimate package to trick installs (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in streak-daykit (npm)

MAL-2026-12466

Immediate action

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

npm uninstall streak-daykit

What this malware does

On import of the package's main entry, a top-level _bootstrap IIFE in index.mjs runs a Linux-gated routine that detects a WSL environment by probing /mnt/c, locates the active Windows user profile via NTUSER.DAT, fetches an executable from a hex-obfuscated URL that decodes to a backlazeb2.com host (a typosquat of Backblaze B2's backblazeb2.com), and writes the payload as vite-native-helper.exe into AppData/Roaming/Microsoft/Windows/Start Menu/Programs/Startup on the host Windows account, establishing user-level autostart persistence. The remote URL, destination path, and dropped filename are all stored as split hex arrays joined at runtime and decoded via Buffer.from(h, 'hex').toString(), and surrounding comments frame the code as environment bootstrap and telemetry routing. No version pin, hash check, or publisher-matching source is present; the fetched binary is opaque attacker-controlled content executed on next Windows sign-in.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

2c7d8d4f5dc118e83eddeb156c2687b1ef439348e3006579eae48f219488cc6b

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for streak-daykit (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-daykit across your stack and pipelines.
If you installed it — respond
streak-daykit is a typosquat — you almost certainly intended a legitimately-named package. Remove streak-daykit, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If streak-daykit 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-daykit 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-daykit 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-014659

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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