Which versions of loveahmedclose are malicious?

The following PyPI versions of loveahmedclose are flagged malicious: 0.0.1, 0.0.2, 0.0.3, 0.0.4, 0.0.5, 0.0.6, 0.0.7, 0.0.8, 0.0.9, 0.0.10. Treat any of these as compromised.

How do I remediate loveahmedclose if I installed it?

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

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

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

Search your lockfiles and build artifacts for loveahmedclose (10 malicious versions).

Malicious package

loveahmedclosePyPI

Advisory published Mar 18, 2026Updated Mar 19, 2026

loveahmedclose is a confirmed malicious PyPI package (MAL-2026-1903) that executes malicious code on install (malicious versions 0.0.1, 0.0.2, 0.0.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in loveahmedclose (PyPI)

MAL-2026-1903

Immediate action

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

pip uninstall loveahmedclose

Malicious versions

10 flagged

0.0.10.0.20.0.30.0.40.0.50.0.60.0.70.0.80.0.90.0.10

Indicators of compromise (SHA-256)

d6d043b3dc72ed6eb45c242ced5da04fce42dfe356baebe51646ff59a6084d84

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for loveahmedclose (10 malicious versions).
If you installed it — respond
Remove loveahmedclose 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 loveahmedclose 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. loveahmedclose on PyPI has been identified as a malicious package (versions 0.0.1, 0.0.2, 0.0.3, 0.0.4, 0.0.5, 0.0.6, 0.0.7, 0.0.8, and 2 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-00478

Credits

ReversingLabs · finder

Detect & block this

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