Which versions of map-streak-kit are malicious?

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

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

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

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

Yes — map-streak-kit is associated with the IN-MAL-2026-017168, GHSA-m55q-8hc5-f46f 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 map-streak-kit 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 map-streak-kit (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 map-streak-kit across your stack and pipelines.

Malicious package

map-streak-kitnpm

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

MAL-2026-13632

Immediate action

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

npm uninstall map-streak-kit

What this malware does

On import, dist/index.mjs chmods 0755 and spawns the bundled Linux x86_64 binary dist/internal/calc-math.dat as a detached background process. The binary is a RedShell-style remote-access implant: it beacons to hardcoded C2 217.60.77.63, executes /bin/sh commands, drops and runs additional ELFs and shellcode fetched from the C2, offers SOCKS5 proxying and TCP port forwarding, installs systemd --user persistence (svc-update.service), and exfiltrates files via POST /api/extract-receive. Implant commands /ssh_keys, /creds, /dbfind, /clipboard, /env, and /dataextract harvest installer-side secrets (SSH private keys, stored credentials, clipboard, environment) and upload them to the same C2 through a chunked BIGEXTRACT upload routine. Package name, README, and inline comments describe the ELF as a 'native math accelerator' for calendar/streak math, but the pure-JS daymath.mjs never invokes the binary; the shipped SHA-256 'integrity check' (4537b118...3466) pins this specific implant, so it functions as anti-tamper for the payload rather than a security control.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

80727943437a7e22116b369c010fc965c4854a0c58a053504c4bc55555e90dd4

14340c09001c59fa53d0926ed49265d43efcb6115df75c49ac24c1358efa007b

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 map-streak-kit (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 map-streak-kit across your stack and pipelines.
If you installed it — respond
map-streak-kit 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 map-streak-kit 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 map-streak-kit 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. map-streak-kit 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-017168GHSA-m55q-8hc5-f46f

References

Credits

Amazon Inspector · finder

Detect & block this

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