Which versions of c8test are malicious?

The following PyPI versions of c8test are flagged malicious: 0.0.1, 0.0.2, 0.0.3. Treat any of these as compromised.

How do I remediate c8test if I installed it?

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

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

Yes — c8test is associated with the RLMA-2025-02996, GENERIC-standard-pypi-install-pentest, RLUA-2026-00175 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 c8test 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 c8test (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging c8test across your stack and pipelines.

Malicious package

c8testPyPI

Malicious code in c8test (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-5099

Immediate action

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

pip uninstall c8test

What this malware does

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.10.0.20.0.3

Indicators of compromise (SHA-256)

16205c7e25e37679811ad0f17c4819981dbb4e36c0cb4aa6a587003fd5b152f1

867c8da2c1a89ddba6aa78c7149bab716bf6500fa707888026657f471bc3353a

b94beda1abe6cca6b53ac1891e3a3baea95df1b8c260dd9f4ea15998e26391b9

0cd4c9d820b432a67a17625f9216b5108646ea5529a20356f5dc71b434c58447

cd35f8b9677dc41a9b173444dc9ea9bbfe97e16be503a30d9ec16d08bfd1276a

1e9004346c91109cc4292bae9c651f18cdc06b3472bd50ecf8f450e1daa97a84

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

Campaign

RLMA-2025-02996GENERIC-standard-pypi-install-pentestRLUA-2026-00175

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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