Which versions of streak-cal-core are malicious?

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

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

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

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

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

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

Malicious package

streak-cal-corenpm

streak-cal-core is a confirmed malicious npm package (MAL-2026-14222) 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-cal-core (npm)

MAL-2026-14222

Immediate action

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

npm uninstall streak-cal-core

What this malware does

index.mjs (the package's main entry) contains a ~500 KB base64-encoded x86-64 ELF payload stored in a _store array disguised with a // --- Calibration Data --- comment. On import, the module joins the base64 chunks, writes the decoded bytes to disk with mode 0o755, dynamically imports node:child_process, and executes the dropped binary. The behavior fires as a top-level import side effect, so any consumer that requires or imports the package runs the embedded native code. The file's header comment labels the module streak-larq-hydration and references svelte-insight-hydration, while the package is published as streak-cal-core with a README pointing at svelte-streak-cal — internal naming does not match the published identity, consistent with a family of sibling typosquat variants. The advertised purpose (dependency-free calendar/streak math helper) is inconsistent with shipping and executing an opaque native binary.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

a4e42ea741c3a61878fa72cd8b7ab4547c52f14b69f429129c46edba70771287

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-cal-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-cal-core across your stack and pipelines.
If you installed it — respond
streak-cal-core is a typosquat — you almost certainly intended a legitimately-named package. Remove streak-cal-core, 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-cal-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-cal-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-cal-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-018318

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks streak-cal-core-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