Malicious Code Vulnerability in namasae-naiuapa-mapo Package
Summary
MAL-2025-161824: Malicious code in namasae-naiuapa-mapo (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 namasae-naiuapa-mapo 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 numerous derivative packages. These packages often contain scripts designed to manipulate package metadata for fraudulent purposes, impacting the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in the namasae-naiuapa-mapo package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which aims to inflate developer reputation scores through deceptive practices. The ramifications include pollution of the npm registry and potential security risks for developers who unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall namasae-naiuapa-mapoIf 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 remove the namasae-naiuapa-mapo package from your project by executing the following command: npm uninstall namasae-naiuapa-mapo. This will prevent the malicious code from executing until a secure version is available.
Conclusion
The namasae-naiuapa-mapo package contains malicious code that poses a significant risk to developers using it. It is crucial to update or remove the package to maintain the integrity of your projects and the npm ecosystem.
See every vulnerability recorded for namasae-naiuapa-mapo →
FAQ
It is an npm package that is part of a token reward campaign, known for flooding the npm registry with derivative packages.
The malicious code modifies your package.json file, potentially leading to security vulnerabilities and pollution of the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
As a workaround, you can uninstall the package to prevent the execution of the malicious code until a secure version is released.
Detailed information can be found in the vulnerability report and by monitoring updates from the npm registry.
