Malicious Code Vulnerability in memlib (PyPI) - MAL-2025-6547

memlib Updated 02 Oct 2025

Summary

31/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6547: Malicious code in memlib (PyPI). Affects memlib versions 2.0.0. 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

memlib is a Python library available on the Python Package Index (PyPI) that provides various memory management functionalities. It is commonly used in applications that require efficient memory handling. However, the library has been identified to contain malicious code, which poses a significant risk to users relying on its functionalities.

Vulnerability Detail

The vulnerability identified as MAL-2025-6547 in the memlib package originates from the inclusion of malicious code in version 2.0.0. This code can potentially compromise the security of applications utilizing this library, leading to unauthorized access, data breaches, or other malicious activities. Users of memlib are at risk of exploitation if they do not take immediate action to address this issue.

How To Fix

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

pip uninstall memlib

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 can avoid using the memlib package until a secure version is released. Additionally, consider using alternative libraries that provide similar memory management functionalities without the associated risks.

Conclusion

The memlib package has been identified with a serious vulnerability due to malicious code in version 2.0.0. Users are strongly advised to uninstall this version and monitor for updates or alternatives to ensure the security of their applications.

See every vulnerability recorded for memlib →

Share this vulnerability

FAQ

The vulnerability involves the presence of malicious code in the memlib package, which can compromise application security.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without any signup.

You should immediately uninstall the affected version (2.0.0) and check for any available patched versions or consider using alternative libraries.

Yes, Vulert can help you monitor your dependencies for vulnerabilities using just the Pipfile.lock, providing real-time alerts.

Failing to address this vulnerability could lead to unauthorized access, data breaches, and other malicious activities affecting your application.

How To Fix

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

pip uninstall memlib

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