Malicious Code Vulnerability in loveclose1 Package

loveclose1 Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1905: Malicious code in loveclose1 (PyPI). Affects loveclose1 versions 0.0.4 – 0.0.9. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The loveclose1 package is a Python library available on PyPI, designed for specific functionalities related to closing operations in applications. It is utilized by developers to streamline processes in their projects. However, recent findings have revealed that certain versions of this package contain malicious code, posing significant security risks to users who integrate it into their applications.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the loveclose1 package, specifically in versions 0.0.4 through 0.0.9. This code can potentially compromise the security of applications that depend on this package, leading to unauthorized access, data breaches, or other harmful consequences. The malicious nature of this code was identified by ReversingLabs, which has documented the issue extensively.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

pip uninstall loveclose1

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary measure, users can remove the loveclose1 package from their projects until a secure version is confirmed. This can be done using the command: 'pip uninstall loveclose1'. Additionally, consider using alternative packages that provide similar functionalities without known vulnerabilities.

Conclusion

The loveclose1 package has been found to contain malicious code in several versions, posing serious security risks to applications that utilize it. Users are urged to update to a secure version or remove the package entirely until a fix is confirmed. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for loveclose1 →

Share this vulnerability

FAQ

Versions 0.0.4 to 0.0.9 of the loveclose1 package are known to contain malicious code.

You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.

It is recommended to uninstall the affected version and update to a secure version of the loveclose1 package as soon as possible.

The vulnerability was identified by ReversingLabs, a cybersecurity firm specializing in threat intelligence.

Using the affected package can lead to unauthorized access to your application, data breaches, and other security incidents.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

pip uninstall loveclose1

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback