Which versions of regexparam are malicious?

The following PyPI versions of regexparam are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate regexparam if I installed it?

Remove regexparam from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed regexparam — how do I know if it already compromised me?

If regexparam was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is regexparam part of a known attack campaign?

Yes — regexparam is associated with the RLMA-2025-04231, RLUA-2025-04808, RLUA-2025-05632 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 regexparam across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for regexparam (version 1.0.0).

Malicious package

regexparamPyPI

Advisory published Aug 28, 2025Updated Dec 2, 2025

regexparam is a confirmed malicious PyPI package (MAL-2025-41736) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in regexparam (PyPI)

MAL-2025-41736

Immediate action

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

pip uninstall regexparam

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

58d488c22d221976212cc3c6d3916a429edad6cfe6796fd4c288e4038010c444

751821acc19bf45f6a4da5baea46c1bbc1cec11d32e4f91a34de8b5c17be1d4c

2bc9cf933b5bd8855434b98935a0cf38d04b585ce28a155fbeba989999036820

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for regexparam (version 1.0.0).
If you installed it — respond
Remove regexparam from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If regexparam was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. regexparam on PyPI has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-04231RLUA-2025-04808RLUA-2025-05632

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks regexparam-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database