Which versions of lalpulsar are malicious?

The following PyPI versions of lalpulsar are flagged malicious: 0.0.0.1. Treat any of these as compromised.

How do I remediate lalpulsar if I installed it?

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

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

Yes — lalpulsar is associated with the RLMA-2025-01968 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 lalpulsar across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for lalpulsar (version 0.0.0.1).

Malicious package

lalpulsarPyPI

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

Malicious code in lalpulsar (PyPI)

MAL-2025-2970

Immediate action

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

pip uninstall lalpulsar

Malicious versions

1 flagged

0.0.0.1

Indicators of compromise (SHA-256)

326464cf654f4d7d65086b70f7fcae164d9ffbcad322505f65ad77a95df8f02a

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for lalpulsar (version 0.0.0.1).
If you installed it — respond
Remove lalpulsar 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 lalpulsar 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. lalpulsar on PyPI has been identified as a malicious package (version 0.0.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-01968

Credits

ReversingLabs · finder

Detect & block this

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