Which versions of osanlizer are malicious?

The following PyPI versions of osanlizer are flagged malicious: 1.0.6, 1.0.7, 1.0.9. Treat any of these as compromised.

How do I remediate osanlizer if I installed it?

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

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

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

Malicious package

osanlizerPyPI

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

MAL-2025-47792

Immediate action

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

pip uninstall osanlizer

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

1.0.61.0.71.0.9

Indicators of compromise (SHA-256)

5a22760876b525a4fb3417d9c18f9cc6f8d804a00186ae32f693af7c307e96ce

0a33afbbe9e8a6dc1ec06ad352415e35243d248fe908c15fe3c26323fcee3e8e

b232b669046429e182e86e8e80a041907ff6d9b135b45e9de1ce17fc05dd4d42

939073c763f1152f73f2b87ae7cdc8853ab09d707c8d6b82433b0eb5b3367809

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

Campaign

RLMA-2025-04797GENERIC-standard-pypi-install-pentestRLUA-2026-00574

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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