Which versions of totallysafe are malicious?

The following PyPI versions of totallysafe are flagged malicious: 2.0.0, 2.0.1. Treat any of these as compromised.

How do I remediate totallysafe if I installed it?

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

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

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

Malicious package

totallysafePyPI

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

MAL-2025-41785

Immediate action

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

pip uninstall totallysafe

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

2 flagged

2.0.02.0.1

Indicators of compromise (SHA-256)

d3e0967bc385e2782be3753eb39a1dd8cb080d8f79c9bb7df9c5505a453244c0

5898b1b8d74afeebb076f30673790ecdab5e0f2ea2679b539927d3e26ee9d8dc

772cdbb82e78ad30e8f4cb0bcdd45aaf61884da051a9998fd1c1431335d0eaf7

72402f60e27370bd76b0d237cfdf198e9a121f31f68ead405c90ecb31fd028a3

947f4dfde44800e371bbce7957cc62c501687a1f00e0520c566fa3faeceae6dc

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

Campaign

RLMA-2025-04283GENERIC-standard-pypi-install-pentestRLUA-2026-00833

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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