Which versions of saml-helper are malicious?

The following PyPI versions of saml-helper are flagged malicious: 2.3.1, 2.5.3, 2.5.4. Treat any of these as compromised.

How do I remediate saml-helper if I installed it?

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

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

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

Malicious package

saml-helperPyPI

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

MAL-2025-5132

Immediate action

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

pip uninstall saml-helper

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

2.3.12.5.32.5.4

Indicators of compromise (SHA-256)

2fd5325ea1bdab3a34b47c7e78f3c035f1479808c746c6e39b26c023ee517e1f

227adfac43512ee4f67aeb5913e27d86b6950e3f7dc888f850c03cb5e2c8d185

2b054dba9521b1260174fa01f3f7ba51d88bd51e53c481675ed967271304a63f

53cae38df3fb11b7030ee7fe4f309882710fc79fe2375dd5f1e0e64b91853fbc

9e7270cb0378022527e2712743992aef4cf5ed526770e35f6efb2d24d1866354

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

Campaign

RLMA-2025-03029GENERIC-standard-pypi-install-pentestRLUA-2026-00744

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks saml-helper-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