Malicious Code Injection in nana-soto70-pore: A Threat to npm Packages
Summary
MAL-2025-98172: Malicious code in nana-soto70-pore (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 'nana-soto70-pore' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is linked to a campaign that aims to exploit the npm registry by flooding it with malicious packages. These packages are designed to inflate developer reputation scores through automated scripts that generate and publish numerous derivative packages with randomized names.
Vulnerability Detail
The vulnerability in 'nana-soto70-pore' originates from its association with the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file by removing private flags, altering 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 integrity of other packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nana-soto70-poreIf 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 'nana-soto70-pore' package and monitor your project for any dependencies that may have inadvertently included it. Use the following command to check for outdated packages: 'npm outdated'.
Conclusion
The 'nana-soto70-pore' package poses a significant risk due to its malicious code designed to exploit the npm registry. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Immediate action is necessary to mitigate the risks associated with this package.
See every vulnerability recorded for nana-soto70-pore →
FAQ
The main issue is that it contains malicious code that modifies package.json files and floods the npm registry with derivative packages.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
You should uninstall the package immediately using 'npm uninstall nana-soto70-pore' and review your other dependencies for security.
Yes, the vulnerability can lead to the pollution of the npm registry and compromise the integrity of other packages, potentially affecting your application's security.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to the packages you use.
