Which versions of karapace-docs are malicious?

The following npm versions of karapace-docs are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate karapace-docs if I installed it?

karapace-docs is a typosquat — you almost certainly intended a legitimately-named package. Remove karapace-docs, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed karapace-docs — how do I know if it already compromised me?

If karapace-docs 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 karapace-docs part of a known attack campaign?

Yes — karapace-docs is associated with the IN-MAL-2026-014931 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 karapace-docs 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 karapace-docs (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging karapace-docs across your stack and pipelines.

Malicious package

karapace-docsnpm

karapace-docs is a confirmed malicious npm package (MAL-2026-12794) that typosquats a legitimate package to trick installs (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in karapace-docs (npm)

MAL-2026-12794

Immediate action

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

npm uninstall karapace-docs

What this malware does

The npm package's preinstall hook runs index.js at install time, which collects the installer's hostname, username, home directory, DNS server list, and the contents of /etc/passwd and /etc/hosts, then POSTs a JSON payload over HTTPS to a hardcoded Burp Collaborator subdomain n6usddpvkn7jcauar9va0xvleck48uwj.oastify.com. The package name mimics a documentation package for karapace (a Kafka registry project), consistent with a dependency-confusion / typosquat recon payload. Installer host identity and local system file contents leave the machine to an attacker-controlled OAST endpoint on npm install with no user interaction.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

a0d1e2b10c31f45e3c73ad895a1ccd4188cdedf5ab1a795b420f5aa2693d7686

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for karapace-docs (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging karapace-docs across your stack and pipelines.
If you installed it — respond
karapace-docs is a typosquat — you almost certainly intended a legitimately-named package. Remove karapace-docs, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If karapace-docs 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 karapace-docs 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. karapace-docs on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014931

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks karapace-docs-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database