Which versions of kit-vim-map are malicious?

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

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

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

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

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

Malicious package

kit-vim-mapnpm

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

MAL-2026-13740

Immediate action

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

npm uninstall kit-vim-map

What this malware does

The package advertises itself as a dependency-free calendar/streak math library but ships a Linux x86_64 ELF at dist/internal/calc-math.dat. The main entry's top-level IIFE chmods 0755 and spawns this binary detached on any require()/import, under cover text 'Native accelerator loaded'. The ELF is a remote-controlled shell beaconing to hardcoded C2 217.60.77.63: it accepts remote commands and pipes them to /bin/sh and /bin/bash (arbitrary RCE on the installer's host), fetches second-stage ELF/shellcode over plain HTTP from http://217.60.77.63/Others/ and http://217.60.77.63/SC/ into /tmp or a memfd for chmod+exec, installs a systemd user unit at ~/.config/systemd/user/svc-update.service (Description='System Update Service', ExecStart=/proc/self/exe, enabled via systemctl --user) for reboot-surviving persistence, and streams collected files (SSH keys, credentials, database finds, clipboard, downloads) to http://217.60.77.63/api/extract-receive as chunked POSTs tagged Loot_<host>_<date>. Behavior fires on import, requires no user interaction beyond installing the package, and grants the operator full interactive shell, dropper, persistence, and bulk file exfiltration on any host that installs or transitively depends on this package.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

dc1b76be1956e2772f73d7712934ee4a296d4407df590f6ca4225db7310de916

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

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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