Which versions of streak-kit-map are malicious?

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

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

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

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

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

Malicious package

streak-kit-mapnpm

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

MAL-2026-13519

Immediate action

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

npm uninstall streak-kit-map

What this malware does

The package advertises itself as a streak/calendar math library, but its main entry dist/index.mjs contains a top-level IIFE that, on any import/require, chmods dist/internal/map-calc.bin to 0755 and detached-spawns it after a sha256 integrity gate. The bundled Linux x86_64 ELF is a full remote-control implant: strings show a RedShell / RC2TUN beacon to a hardcoded C2 at 217.60.77.63, command handlers for shell execution, ELF/shellcode download-and-run (including memfd_create fd exec) via HTTP paths /Others/<file> and /SC/<file>, SOCKS5 proxy and port forwarding, chunked file exfiltration via POST /api/extract-receive HTTP/1.1 packaging loot as Loot_<host>_<user>_<ts>, targeted collection of SSH keys and credentials (/ssh_keys, /creds, /dbfind, /download, /dataextract), and reboot persistence by writing ~/.config/systemd/user/svc-update.service (Description=System Update Service, Restart=always) and enabling it via systemctl --user. The JS wrapper's Loads the native math accelerator / integrity verification — critical security gate comments are cover-story framing; the hash pin exists to guarantee the exact malicious bytes execute.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

18948f1c8e71b24d05e1ef6f749995bdc9098d610f791b86dc33f7d41dd8b1d3

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

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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