Which versions of karapace-docs are malicious?

The following npm versions of karapace-docs are flagged malicious: 1.0.1, 1.1.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 installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is karapace-docs part of a known attack campaign?

Yes — karapace-docs is associated with the IN-MAL-2026-014931, GHSA-mf8g-pqcc-wxfw, IN-MAL-2026-019821 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?

Search your lockfiles and build artifacts for karapace-docs (2 malicious versions).

Malicious package

karapace-docsnpm

Advisory published Aug 5, 2026Updated Sep 9, 2026

karapace-docs is a confirmed malicious npm package (MAL-2026-12794) that typosquats a legitimate package to trick installs (malicious versions 1.0.1, 1.1.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.

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

2 flagged

1.0.11.1.1

Indicators of compromise (SHA-256)

a0d1e2b10c31f45e3c73ad895a1ccd4188cdedf5ab1a795b420f5aa2693d7686

0504b1eeee4b53817289d98df2d4b44775e97feea2be622a724012a4dc60576f

f06b8b81224d46fc5efc33c0776f3521a77f11b4bf6194acdbc5d32557fb6bbe

Detection & response playbook

Typosquat

Find it
Search your lockfiles and build artifacts for karapace-docs (2 malicious versions).
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 installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. karapace-docs on npm has been identified as a malicious package (versions 1.0.1, 1.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014931GHSA-mf8g-pqcc-wxfwIN-MAL-2026-019821

References

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