Which versions of kit-map-vim are malicious?

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

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

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

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

Yes — kit-map-vim is associated with the IN-MAL-2026-017608, GHSA-hg96-r46x-6f4w 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 kit-map-vim 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 kit-map-vim (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 kit-map-vim across your stack and pipelines.

Malicious package

kit-map-vimnpm

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

MAL-2026-13915

Immediate action

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

npm uninstall kit-map-vim

What this malware does

On import of kit-map-vim, dist/index.mjs unconditionally spawns dist/internal/calc-math.dat as a detached child process after a SHA-256 self-check. The.dat file is a Linux x86_64 ELF RedShell remote-access implant disguised as a 'native math accelerator'. The implant beacons to hardcoded C2 host 217.60.77.63 over plain HTTP and exposes command handlers that download and execute additional ELF binaries and shellcode from http://217.60.77.63/Others/* and /SC/* endpoints, including in-memory execution via memfd_create/fexecve to avoid touching disk. It installs a masquerading systemd user unit 'svc-update.service' (Description=System Update Service, Restart=always) for persistence, provides SOCKS5 proxy and TCP port-forwarding, and offers built-in commands to enumerate users/env/processes/network configuration, harvest SSH keys and credentials from ~/.ssh and credential stores, and stream arbitrary filesystem paths to the operator via a chunked 'POST /api/extract-receive' handler labeled with a 'Loot_*' destination. The package's stated day-math purpose has no need for a native binary; the ELF's exposed command set (RedShell) is unrelated to any math functionality.

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)

03873a12af48745e3fd5173ce736267aebd3290be427275073562b8e1ada61fc

4eb4b412fdc46f4d5569e4b581cf64a9e1bed94cc7cd8fcd91613b98f73ac20f

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 kit-map-vim (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 kit-map-vim across your stack and pipelines.
If you installed it — respond
kit-map-vim 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 kit-map-vim 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 kit-map-vim 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. kit-map-vim 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-017608GHSA-hg96-r46x-6f4w

References

Credits

Amazon Inspector · finder

Detect & block this

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