Which versions of loveclose2 are malicious?

The following PyPI versions of loveclose2 are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate loveclose2 if I installed it?

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

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

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

Search your lockfiles and build artifacts for loveclose2 (version 0.0.1).

Malicious package

loveclose2PyPI

Advisory published Mar 18, 2026Updated Mar 19, 2026

loveclose2 is a confirmed malicious PyPI package (MAL-2026-1906) that executes malicious code on install (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in loveclose2 (PyPI)

MAL-2026-1906

Immediate action

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

pip uninstall loveclose2

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

8f9e400cb6ee08597b193ea173162e551fc6a0a6d01aa04f7047509eb7c57c55

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-00481

Credits

ReversingLabs · finder

Detect & block this

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