Malicious Code Exfiltration in composer-dev Package

composer-dev Updated 20 Mar 2026

Summary

20/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1987: Malicious code in composer-dev (PyPI). Affects composer-dev versions 9.9.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 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 composer-dev package, available on PyPI, is intended for development purposes within Python environments. It is designed to assist developers in managing dependencies and enhancing their workflow. However, this package has been identified as malicious, containing code that exfiltrates sensitive information from the host system, such as IP addresses and usernames, posing a significant security risk to users who install it.

Vulnerability Detail

The vulnerability stems from the malicious code embedded in the composer-dev package, which overrides the install command in setup.py to execute harmful actions during installation. This code is designed to exfiltrate basic information about the host, making it a potential threat to user privacy and security. The package has no legitimate functionality beyond this malicious intent, and its installation can lead to unauthorized data access.

How To Fix

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

pip uninstall composer-dev

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

There are no specific workarounds for this vulnerability, as the best course of action is to completely avoid the use of the composer-dev package. If you need similar functionality, consider using alternative packages that are well-reviewed and have a good security track record.

Conclusion

The composer-dev package poses a significant security risk due to its malicious code that exfiltrates sensitive information from the host system. Users are advised to uninstall this package and avoid using it in the future. Regular monitoring of open-source vulnerabilities using tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for composer-dev →

Share this vulnerability

FAQ

The composer-dev package is a Python package intended for development purposes, but it has been identified as malicious.

The malicious code in the composer-dev package exfiltrates basic information such as the host's IP address and username.

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

Currently, there is no safe or patched version of the composer-dev package available. It is recommended to avoid using it.

If you have installed composer-dev, you should uninstall it immediately using the command 'pip uninstall composer-dev'.

How To Fix

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

pip uninstall composer-dev

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