Which versions of decapod-common are malicious?

The following PyPI versions of decapod-common are flagged malicious: 0.0.0, 1.2.dev1, 1.2.dev2. Treat any of these as compromised.

How do I remediate decapod-common if I installed it?

decapod-common 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 decapod-common — how do I know if it already compromised me?

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

Yes — decapod-common is associated with the GENERIC-standard-pypi-install-pentest, IN-MAL-2026-015994, IN-MAL-2026-016000, IN-MAL-2026-015997 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 decapod-common 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 decapod-common (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging decapod-common across your stack and pipelines.

Malicious package

decapod-commonPyPI

decapod-common is a confirmed malicious PyPI package (MAL-2026-13386) that steals credentials and exfiltrates sensitive data (malicious versions 0.0.0, 1.2.dev1, 1.2.dev2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in decapod-common (PyPI)

MAL-2026-13386

Immediate action

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

pip uninstall decapod-common

What this malware does

setup.py overrides the install command to collect the installer's hostname and resolved IP address via socket.gethostname()/gethostbyname() and POST them as JSON to a hardcoded webhook.site endpoint (https://webhook.site/f79bb373-481e-4116-b3d1-35005970b62f) before completing installation. The beacon fires automatically during pip install of the sdist. The package's own metadata describes it as a POC beacon; no legitimate functionality accompanies the network callout.

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-standard-pypi-install-pentest

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

3 flagged

0.0.01.2.dev11.2.dev2

Indicators of compromise (SHA-256)

335a31b4299781e6a6926da0b85d6f1b2e22aaefbb5953418b7abe7aa0ada4bd

4a2befb40c79b92c5ebe20409768c0aa0da5a17e6be0cab991ef2a631aaa949f

1ff269b55a031b0c07059dc8664cd22e88e0015e25eec6e9252662ed3a585365

e0de84c80d520754e010d02b90fd4dc728d90fa9efe8c1e8cc6ddd7eb05e0da4

058b86879038ce7ef09b6764fbdd9d82af912b98bd9348d067e3540c537ff9a5

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 decapod-common (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging decapod-common across your stack and pipelines.
If you installed it — respond
decapod-common 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 decapod-common 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 decapod-common 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. decapod-common on PyPI has been identified as a malicious package (versions 0.0.0, 1.2.dev1, 1.2.dev2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GENERIC-standard-pypi-install-pentestIN-MAL-2026-015994IN-MAL-2026-016000IN-MAL-2026-015997

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks decapod-common-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