Malicious Code Injection in mahnud-nofty-muta: A Threat to npm Users
Summary
MAL-2025-159105: Malicious code in mahnud-nofty-muta (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 'mahnud-nofty-muta' is part of the npm ecosystem and has been identified as part of a malicious campaign targeting developers involved with the tea.xyz token reward system. This package is designed to manipulate the npm registry by creating and publishing numerous derivative packages with altered metadata, which can mislead users and inflate developer reputation scores.
Vulnerability Detail
The vulnerability in 'mahnud-nofty-muta' originates from its design to execute autopublish scripts that modify the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. This malicious behavior can compromise the integrity of the npm ecosystem, potentially affecting developers who rely on these packages for legitimate purposes.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall mahnud-nofty-mutaIf 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 avoid using 'mahnud-nofty-muta' and any packages that depend on it. Additionally, consider using npm audit to identify and address vulnerabilities in your project dependencies.
Conclusion
The 'mahnud-nofty-muta' package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, developers can safeguard their projects from such threats.
See every vulnerability recorded for mahnud-nofty-muta →
FAQ
The main risk is that it can alter your package.json file and publish malicious variants, compromising your project's integrity.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.
You should remove the package immediately and check for any other dependencies that may have been affected.
Regularly audit your dependencies using tools like npm audit and stay updated on security advisories related to the packages you use.
Signs include unexpected changes in package.json, unfamiliar package names, or unusual behavior in your application.
