Which versions of ctftestsowwy are malicious?

The following PyPI versions of ctftestsowwy are flagged malicious: 0.0.1, 0.0.2, 0.0.3, 0.0.4, 0.0.6, 0.0.7, 0.0.8, 0.0.9, 0.1.0, 0.1.1, 0.1.4, 6.9, 7. Treat any of these as compromised.

How do I remediate ctftestsowwy if I installed it?

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

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

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

Malicious package

ctftestsowwyPyPI

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

MAL-2025-4213

Immediate action

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

pip uninstall ctftestsowwy

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

13 flagged

0.0.10.0.20.0.30.0.40.0.60.0.70.0.80.0.90.1.00.1.10.1.46.97

Indicators of compromise (SHA-256)

b9fa8fb131f37c1ac35f8837eac1cc4294fdd47bb73149db6c7fcd09100ca985

c490c38cbe03c8edc938141679452826d6cd4a2626e02afb064ba47a97cc5859

d6e53c512e63c328ecdc02187c5fe11c5b379e6bf451f936f769219c1787d146

967463eb5a6fc1908a95c9a0f5825d8a47695e42640d31fd7b77358201afa101

068a9aaf3c2853dd9379ec95c7ab7e66598f1221c6d57fea86d4ce4a8d6e822c

6065b0a3b0eade6c004127632c0c683a7c67be0dd942b4d6c78e5954cc819be7

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

Campaign

RLMA-2025-02565GENERIC-standard-pypi-install-pentestRLUA-2026-00241

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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