Which versions of kampodra are malicious?

The following npm versions of kampodra are flagged malicious: 0.8.16. Treat any of these as compromised.

How do I remediate kampodra if I installed it?

Remove kampodra from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed kampodra — how do I know if it already compromised me?

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

Yes — kampodra is associated with the GHSA-57xg-9jqp-97gm 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 kampodra across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for kampodra (version 0.8.16).

Malicious package

kampodranpm

Advisory published Nov 13, 2026Updated Nov 13, 2026

kampodra is a confirmed malicious npm package (MAL-2026-19258) that executes malicious code on install (malicious version 0.8.16). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in kampodra (npm)

MAL-2026-19258

Immediate action

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

npm uninstall kampodra

What this malware does

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

0.8.16

Indicators of compromise (SHA-256)

92db23fff21ab5c252dd2bda64ec925ac53b0111485accc0b2572d22b624f49d

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for kampodra (version 0.8.16).
If you installed it — respond
Remove kampodra from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If kampodra 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. kampodra on npm has been identified as a malicious package (version 0.8.16 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-57xg-9jqp-97gm

References

github.com

Detect & block this

O3 blocks kampodra-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