Which versions of streak-day-engine are malicious?

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

How do I remediate streak-day-engine if I installed it?

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

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

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

Malicious package

streak-day-enginenpm

streak-day-engine is a confirmed malicious npm package (MAL-2026-12462) 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-day-engine (npm)

MAL-2026-12462

Immediate action

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

npm uninstall streak-day-engine

What this malware does

index.mjs runs a hex-obfuscated top-level async IIFE at module import time. Identifiers and payload constants (process, fetch, child_process, fs/promises, target paths, URL, tar command, VBS template) are stored hex-encoded in a _c table and decoded via Buffer.from(h, 'hex').toString(). On import, the code fetches https://f004.backblazeb2.com/file/dp8hbvocjd2fpza/helper.tar.gz, writes the archive under the user's AppData directory, extracts it via tar -xzf, and writes a VBS launcher (vite-native-helper.vbs) into AppData/Roaming/Microsoft/Windows/Start Menu/Programs/Startup that uses CreateObject("WScript.Shell").Run p, 0, False to invoke the extracted RenameMe.exe hidden at every user login. Result: attacker-controlled bytes land on the installer's host on import/require of the package, and a login-persistent execution channel is established via the Windows Startup folder.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

fb1b5dba41de915e2ef23790e3e92b3839b9a52e5196480d12ae8a7a8208cf82

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-day-engine (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-day-engine across your stack and pipelines.
If you installed it — respond
Remove streak-day-engine 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-day-engine 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-day-engine 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-day-engine 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-014675

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks streak-day-engine-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