Critical Malicious Code Vulnerability in loveclose2 Package

loveclose2 Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1906: Malicious code in loveclose2 (PyPI). Affects loveclose2 versions 0.0.1. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The loveclose2 package is a Python library available on PyPI, designed for specific functionalities related to closing love letters in a creative manner. It is utilized by developers looking to add unique features to their applications. However, this package has been identified with a significant vulnerability that exposes users to potential malicious code execution.

Vulnerability Detail

The vulnerability in the loveclose2 package arises from the presence of malicious code that can be exploited by attackers. This code may lead to unauthorized access, data breaches, or other harmful actions within the user's environment. The issue was reported by ReversingLabs and is linked to version 0.0.1 of the package. Users who have installed this version are at risk and should take immediate action to mitigate potential threats.

How To Fix

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

pip uninstall loveclose2

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 workaround, users are advised to uninstall the loveclose2 package until a secure version is released. This can be done using the command: 'pip uninstall loveclose2'. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The loveclose2 package has been identified with a critical vulnerability due to malicious code. Users are urged to take immediate action by uninstalling the package and monitoring for updates. Utilizing tools like Vulert can help in real-time monitoring of open-source vulnerabilities.

See every vulnerability recorded for loveclose2 →

Share this vulnerability

FAQ

The loveclose2 package is a Python library designed for creative functionalities related to love letters.

The vulnerability involves malicious code that can lead to unauthorized access and potential data breaches.

You can use Vulert's playground at Vulert Scanner to check if your application is affected without any signup.

It is recommended to uninstall the loveclose2 package until a secure version is available.

Currently, there is no patched version available for the loveclose2 package. Users should monitor the repository for updates.

How To Fix

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

pip uninstall loveclose2

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