Malicious Code Injection in miloa-nditu-nastu: A Threat to npm Packages
Summary
MAL-2025-160443: Malicious code in miloa-nditu-nastu (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 miloa-nditu-nastu 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. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to developers and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in miloa-nditu-nastu originates from its association with a malicious campaign that modifies the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the security and reliability of applications relying on these packages. The malicious payload is designed to exploit the npm ecosystem for token rewards, making it a serious concern for developers.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall miloa-nditu-nastuIf 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 measure, you can avoid using the miloa-nditu-nastu package and replace it with a trusted alternative. Always review the dependencies in your package-lock.json file for any suspicious packages.
Conclusion
The miloa-nditu-nastu package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, developers can protect their applications from potential risks associated with malicious packages.
See every vulnerability recorded for miloa-nditu-nastu →
FAQ
miloa-nditu-nastu is an npm package that is part of a malicious campaign aimed at manipulating the npm registry for token rewards.
The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and functionality.
You should uninstall the miloa-nditu-nastu package immediately using the command npm uninstall miloa-nditu-nastu.
You can use Vulert to monitor your project for open-source vulnerabilities in real-time. It analyzes your package-lock.json file without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
