Malicious Code Injection in mattu-miop-nuaio: A Threat to npm Users
Summary
MAL-2025-160231: Malicious code in mattu-miop-nuaio (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The package 'mattu-miop-nuaio' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'mattu-miop-nuaio' originates from its inclusion in a campaign that floods the npm registry with malicious packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of these variants, which pollutes the npm registry and can potentially harm developers relying on legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall mattu-miop-nuaioIf 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, you can prevent the installation of the vulnerable package by using the following command: npm uninstall mattu-miop-nuaio. Additionally, consider using npm audit to identify and address vulnerabilities in your project.
Conclusion
The 'mattu-miop-nuaio' package presents a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remain vigilant, update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for mattu-miop-nuaio →
FAQ
The vulnerability involves malicious code that modifies package.json files and floods the npm registry with derivative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.
The consequences include the pollution of the npm registry, which can lead to developers inadvertently using compromised packages, affecting their applications' security.
Yes, regularly audit your dependencies using npm audit and remove any vulnerable packages. Additionally, consider using tools like Vulert for real-time monitoring.
If no patched version is available, it is advisable to remove the package from your project to eliminate the risk of exploitation.
