Which versions of titifel-pyip are malicious?

The following PyPI versions of titifel-pyip are flagged malicious: 6.0.0, 7.0.0, 8.0.0. Treat any of these as compromised.

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

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

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

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

Malicious package

titifel-pyipPyPI

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

MAL-2025-47803

Immediate action

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

pip uninstall titifel-pyip

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

3 flagged

6.0.07.0.08.0.0

Indicators of compromise (SHA-256)

488190f06a9c8848fcd78f701b5057e23613422efa2fb60226bcf62040ab5794

30e6c2e5868548463e11674303622528dd91a35b2054d3eea449624364558bd6

db04496b1d3e7bb6d0e4f13530466504551bf243744fb5f0748195d38a11b0f3

e87ccd5be9e1b14985a195aa45d21bb87071f94700959587b815d6335c723b59

546dd95ce05502aa89042eaeae18e7946e3f64234ffe82eca3e78416dedcd967

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

Campaign

RLMA-2025-04813GENERIC-standard-pypi-install-pentestRLUA-2026-00826

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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