Which versions of cicd-ppe-redteam-test02 are malicious?

The following PyPI versions of cicd-ppe-redteam-test02 are flagged malicious: 1.0.0, 1.0.2, 1.0.3. Treat any of these as compromised.

How do I remediate cicd-ppe-redteam-test02 if I installed it?

cicd-ppe-redteam-test02 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 cicd-ppe-redteam-test02 — how do I know if it already compromised me?

If cicd-ppe-redteam-test02 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 cicd-ppe-redteam-test02 part of a known attack campaign?

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

Malicious package

cicd-ppe-redteam-test02PyPI

Malicious code in cicd-ppe-redteam-test02 (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-1064

Immediate action

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

pip uninstall cicd-ppe-redteam-test02

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.

The OpenSSF Package Analysis project identified 'cicd-ppe-redteam-test02' @ 1.0.0 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

3 flagged

1.0.01.0.21.0.3

Indicators of compromise (SHA-256)

962e74263ad015f9bf70c19c2cc90554bbbc43c2840280630cef7904557f1665

834174cff8fb0aa4397db82631cdbfbb9f8f0359fd7187094f0c4b87bb7f9f38

14adb6733ca8f958770b9766a7f255fbd8562886dce3b42cee772eac50e52d0f

f0c2b26eb68525cf02ab5097c16efc774d3881b4955aea6c7b2358869772244c

e0c28a362535d716868eca75de23d46937f2558428f599e823205ef9a1a76535

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

Campaign

GENERIC-standard-pypi-install-pentestRLMA-2026-00194

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter
OpenSSF: Package Analysis · finder
ReversingLabs · finder

Detect & block this

O3 blocks cicd-ppe-redteam-test02-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