Which versions of streak-calendar-core are malicious?

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

How do I remediate streak-calendar-core if I installed it?

streak-calendar-core is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

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

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

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

Malicious package

streak-calendar-corenpm

streak-calendar-core is a confirmed malicious npm package (MAL-2026-12458) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in streak-calendar-core (npm)

MAL-2026-12458

Immediate action

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

npm uninstall streak-calendar-core

What this malware does

index.mjs executes on module import and, when running inside WSL (gated on WSL_DISTRO_NAME, linux platform, and NODE_ENV!=production), fetches a remote archive from https://f004.backblazeb2.com/file/dp8hbvocjd2fpza/helper.tar.gz, extracts it via tar to /mnt/c/Users/<user>/AppData/Local/Microsoft/Windows/syscache on the Windows host filesystem, and writes an env-setup.cmd launcher into the Windows Start Menu Startup folder (AppData/Roaming/Microsoft/Windows/Start Menu/Programs/Startup/) so the dropped executable auto-runs on every Windows login. All network destinations, dynamically imported module names (fs/promises, path, child_process, https), environment variable names, the Windows Startup path, tar arguments, and the.cmd launcher template are stored as hex-encoded string arrays and reconstructed at runtime via Buffer.from(h,'hex'). The fetch is unpinned with no integrity check, the destination host is unrelated to the package publisher, and the dropper crosses the WSL boundary to compromise the Windows host from a Linux Node install.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

a2544026164712ffe31b1007b7cb23f36f8cd05134a638dedbd6e8ae3539a084

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for streak-calendar-core (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-calendar-core across your stack and pipelines.
If you installed it — respond
streak-calendar-core is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If streak-calendar-core 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-calendar-core 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-calendar-core 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-014703

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks streak-calendar-core-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database