Which versions of streak-daily-lib are malicious?

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

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

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

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

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

Malicious package

streak-daily-libnpm

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

MAL-2026-11150

Immediate action

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

npm uninstall streak-daily-lib

What this malware does

On import of index.mjs, setImmediate invokes a _syncWorkspace routine whose network destination and paths are reconstructed at runtime from hex-encoded string arrays (a _cfg object decoded via Buffer.from(s,'hex').toString()). The decoded host is f004.backblazeb2.com and the path prefix is /file/dp8hbvocjd2fpza/. Execution is gated on Linux with WSL_DISTRO_NAME set. The code downloads helper.tar.gz and a background-service binary via https.get, writes them to disk, extracts the tarball with tar -xzf, chmods the service to 0755, and launches it detached with.unref(). It then reaches through the WSL /mnt/c mount into the Windows host filesystem, drops vite.exe under %APPDATA%\Local\Microsoft\Windows\syscache, and writes env-setup.cmd into %APPDATA%\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\ containing start /b /min "" "[BIN]" so the fetched Windows binary runs minimized on every login. The stated purpose of the package is calendar/streak math; none of the fetched hosts, opaque binaries, hex-obfuscated identifiers, or Windows Startup writes align with that purpose. Combined signals present: import-time auto-execution, hex-obfuscated attacker-controlled host, unpinned/unverified binary download and execute, WSL-to-Windows-host escape, and login persistence.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

8664341251bd6864f5aaf9692c5b7bd0945125853bc304c91709aaa335be38f1

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

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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