Malicious Code Injection in mans-matdu-hum Package - npm Vulnerability

mans-matdu-hum Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-159706: Malicious code in mans-matdu-hum (npm). Affected versions are not published. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The mans-matdu-hum package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary function of these packages is to manipulate developer reputation scores through automated publishing scripts, making them a significant threat to the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the mans-matdu-hum package stems from its inclusion in a campaign that generates and publishes derivative packages with randomized names. This malicious code modifies the package.json file by removing private flags, altering version numbers, and continuously republishing variants to pollute the npm registry. The ramifications include potential security risks for developers who unknowingly use these packages, as they can lead to compromised applications and loss of trust in the npm ecosystem.

How To Fix

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

npm uninstall mans-matdu-hum

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 an immediate workaround, you can remove the mans-matdu-hum package from your project by executing the following command: npm uninstall mans-matdu-hum. This will prevent any potential exploitation of the vulnerability until a secure version is released.

Conclusion

The mans-matdu-hum package poses a significant security risk due to its malicious code designed to manipulate npm's package registry. It is essential for developers to stay informed about such vulnerabilities and take proactive measures to secure their applications. Regularly updating dependencies and utilizing tools like Vulert can help mitigate these risks.

See every vulnerability recorded for mans-matdu-hum →

Share this vulnerability

FAQ

The mans-matdu-hum package is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By checking your package-lock.json file, you can determine if your application is affected by this vulnerability.

Using the mans-matdu-hum package can lead to security vulnerabilities in your application, including potential data breaches and loss of trust in your software.

To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and ensure you only install packages from trusted sources.

If you have already used the mans-matdu-hum package, it is crucial to uninstall it immediately and review your project for any potential security impacts.

How To Fix

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

npm uninstall mans-matdu-hum

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