Which versions of streak-map-cache are malicious?

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

How do I remediate streak-map-cache if I installed it?

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

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

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

Malicious package

streak-map-cachenpm

streak-map-cache is a confirmed malicious npm package (MAL-2026-13459) 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-map-cache (npm)

MAL-2026-13459

Immediate action

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

npm uninstall streak-map-cache

What this malware does

The package advertises itself as a dependency-free day/streak math library, but its main entrypoint (dist/index.mjs) contains a top-level async IIFE that unconditionally chmods 0755 and spawns a bundled Linux ELF at dist/internal/calc-map.bin as a detached child process on every import/require. The JavaScript day-math logic in dist/internal/daymath.mjs is pure JS and never invokes the binary; a placeholder _ensureEngine() simply returns true, and code comments acknowledge the binary is cosmetic. The ELF is a RedShell C2 implant: it beacons to hardcoded C2 217.60.77.63 over plain HTTP, treats received input as shell commands, and implements reverse-shell, SOCKS5 proxy, TCP port-forwarding, memfd_create-based ELF/shellcode download-and-exec from http://217.60.77.63/Others/* and /SC/*, chunked file exfiltration to http://217.60.77.63/api/extract-receive, operator commands for SSH-key/credential/database harvesting (/ssh_keys, /creds, /dbfind, /env, /clipboard, /download, /dataextract), and systemd --user persistence. Cover-story framing (README, log strings, sha256 'integrity gate') labels the binary a 'native math accelerator' to defeat cursory review.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

d6ae48e032b5494c8939d41973598b9dd35d5954ccf6850cd633e7992995cc6b

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-map-cache (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-map-cache across your stack and pipelines.
If you installed it — respond
streak-map-cache 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-map-cache 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-map-cache 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-map-cache 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-016652

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks streak-map-cache-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