Which versions of ctf-aio-tool are malicious?

The following PyPI versions of ctf-aio-tool are flagged malicious: 0.1. Treat any of these as compromised.

How do I remediate ctf-aio-tool if I installed it?

ctf-aio-tool establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed ctf-aio-tool — how do I know if it already compromised me?

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

Yes — ctf-aio-tool is associated with the RLMA-2025-01950, 2025-03-marinff, RLUA-2026-00240 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 ctf-aio-tool 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 ctf-aio-tool (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ctf-aio-tool across your stack and pipelines.

Malicious package

ctf-aio-toolPyPI

Malicious code in ctf-aio-tool (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-2952

Immediate action

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

pip uninstall ctf-aio-tool

What this malware does

Installing the package starts a reverse shell. The remote server is, however, set as a local IP, so it's most probably testing

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: 2025-03-marinff

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.
obfuscation
The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine.

Malicious versions

1 flagged

0.1

Indicators of compromise (SHA-256)

15855052cac4115b769ad8f63158e9708ff24c0e4596a7174415ce0ed9fe0ac4

8c915ca4b577d6380c63b138e4d426ed48dd2c496e89c608b416233b80f80511

1641f444ea0056686d1421b67d63c1a6fd944999ed4dff175924de88f1d5182a

d27c34e9826285dd4783352238d8239341528e2eaa4857cf573f60a4e4dbcc6c

cbadcb82a3b4e958399fc48a0d790894456d1cd83a1dc808d0ae9312479f2289

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ctf-aio-tool (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ctf-aio-tool across your stack and pipelines.
If you installed it — respond
ctf-aio-tool establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If ctf-aio-tool 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 ctf-aio-tool 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. ctf-aio-tool on PyPI has been identified as a malicious package (version 0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-019502025-03-marinffRLUA-2026-00240

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks ctf-aio-tool-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring