Which versions of c8tks94kspjghtb are malicious?

The following PyPI versions of c8tks94kspjghtb are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate c8tks94kspjghtb if I installed it?

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

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

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

Malicious package

c8tks94kspjghtbPyPI

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

MAL-2025-5100

Immediate action

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

pip uninstall c8tks94kspjghtb

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

1 flagged

0.0.1

Indicators of compromise (SHA-256)

6ba5b641f31baa7dd3a26587287a3c5ec3cadecf0d04de491dd2fdaeb2fc459f

4138405673a83e5ba271392c52aecd7cb973dfca1a3d7ebff7fcec16868f3a59

9182e332ef5bf851522bb14086c5159f1c606fb90094722f856c87f36e382da7

0d8287fa9cc11fd0ae118df2d85515fb347f266a600364b91cea9a89aec8cb6e

003263b4f47bb84300d6149562c705564f4b8a185c0327eb4b1eccfcfb4786df

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

Campaign

RLMA-2025-02997GENERIC-standard-pypi-install-pentestRLUA-2026-00176

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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