Malicious Code Injection in nokire-namiresan77: A Threat to npm Ecosystem
Summary
MAL-2025-163133: Malicious code in nokire-namiresan77 (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 'nokire-namiresan77' is part of a broader campaign targeting the npm ecosystem, specifically linked to the tea.xyz token reward initiative. This package is designed to automate the generation and publication of derivative packages, which can inflate developer reputation scores in exchange for token rewards. Its functionality is compromised by malicious scripts that manipulate package metadata, posing significant risks to developers and users alike.
Vulnerability Detail
The vulnerability in 'nokire-namiresan77' originates from its association with malicious autopublish scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and create random package names, leading to the continuous republishing of variants that pollute the npm registry. This not only undermines the integrity of the npm ecosystem but also exposes users to potential security risks from unverified packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-namiresan77
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 a temporary workaround, you can avoid using the 'nokire-namiresan77' package and replace it with a trusted alternative. Always verify the integrity of packages before installation.
Conclusion
The 'nokire-namiresan77' package poses a significant threat to the npm ecosystem due to its malicious code and the potential for exploitation. It is essential for developers to remain vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, you can safeguard your applications from such risks.
See every vulnerability recorded for nokire-namiresan77 →
FAQ
The main risk is the potential for malicious code execution, which can compromise your application and expose sensitive data.
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.
You should uninstall the package immediately using 'npm uninstall nokire-namiresan77' and review your project for any other potentially malicious packages.
Yes, consider using well-established and trusted packages that serve similar functionalities without the associated risks.
Regularly audit your dependencies, use tools like Vulert for monitoring, and only install packages from reputable sources.