Which versions of titifel-pypi are malicious?

The following PyPI versions of titifel-pypi are flagged malicious: 0.0.1, 1.0.0, 2.0.1, 3.0.0, 4.0.0, 5.0.0. Treat any of these as compromised.

How do I remediate titifel-pypi if I installed it?

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

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

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

Malicious package

titifel-pypiPyPI

Malicious code in titifel-pypi (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-47804

Immediate action

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

pip uninstall titifel-pypi

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

6 flagged

0.0.11.0.02.0.13.0.04.0.05.0.0

Indicators of compromise (SHA-256)

efdf0ee934d3cc5fe3d2af2f4d0e42785b2ded2b6585f9045fd7af886d4a51b3

2c91ce1180e7135a9da0f34341856b4c20e4dd9e6774623b62adff0fd3f6fde0

246211906386c6795c3728d15bf42f5b9083257d1964d8dc21bcda833dd6363c

44493149ca6a0198d222aa4467836f35e4f54719b46ea2d6a29b4ecb18a7bb42

36b5079c03fe087893d58022d883f8003aef6983056373104d200419ba662c55

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

Campaign

RLMA-2025-04814GENERIC-standard-pypi-install-pentestRLUA-2026-00827

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks titifel-pypi-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