Which versions of streak-day-primitives are malicious?

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

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

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

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

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

Malicious package

streak-day-primitivesnpm

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

MAL-2026-12463

Immediate action

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

npm uninstall streak-day-primitives

What this malware does

The package advertises itself as dependency-free calendar-day arithmetic, but index.mjs contains top-level code that runs on import. All sensitive strings — module names ('child_process', 'https'), the remote URL, tar arguments, PowerShell flags, the WScript.Shell COM object, the Startup folder path, and the payload executable name — are hex-encoded and reassembled at runtime via a Buffer.from(s,'hex').toString() helper (_d + _k table) to hide the payload from static review. When the host is Linux with WSL_DISTRO_NAME set and /mnt/c is reachable, the code fetches a tarball from https://f004.backblazeb2.com/file/dp8hbvocjd2fpza/helper.tar.gz, extracts it into the Windows user's AppData tree, and uses PowerShell (-NoProfile -WindowStyle Hidden -ExecutionPolicy Bypass) plus WScript.Shell CreateShortcut to drop a.lnk pointing at the extracted RenameMe.exe into the Windows user's Startup folder. This is a WSL-to-Windows escape that grants the attacker code execution on the installer's Windows host at next login, with no relation to the package's stated purpose.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

2c4f0cfff000aa550229c0148bf96c70335e4d37048fa9f8fda3d4391ea2249b

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

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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