Malicious Code Injection in nabila-poke53: A Threat to npm Ecosystem
Summary
MAL-2025-161253: Malicious code in nabila-poke53 (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
nabila-poke53 is an npm package that is part of a larger campaign aimed at exploiting the npm registry. This package, like many others in the tea.xyz token reward scheme, is designed to manipulate developer reputation scores by flooding the registry with derivative packages. It is crucial for developers to understand the risks associated with using such packages, as they can lead to significant security vulnerabilities.
Vulnerability Detail
The vulnerability in nabila-poke53 stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is part of a broader scheme to inflate developer reputation scores for token rewards. The malicious payload continuously republishes variants, polluting the npm registry and potentially compromising the integrity of dependent projects. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has been identified as a source of numerous malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nabila-poke53If 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 nabila-poke53 package and replace it with a trusted alternative. Additionally, consider using npm audit to identify and address vulnerabilities in your project's dependencies.
Conclusion
The nabila-poke53 package poses a significant risk due to its malicious code designed to manipulate the npm registry. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can enhance your security posture by providing real-time alerts for open-source vulnerabilities.
See every vulnerability recorded for nabila-poke53 →
FAQ
nabila-poke53 is an npm package that is part of a malicious campaign aimed at manipulating developer reputation scores.
The vulnerability can lead to the injection of malicious code, compromising the integrity of your project and potentially exposing it to further attacks.
You can use tools like npm audit or check your package-lock.json with Vulert to monitor for vulnerabilities in your dependencies.
You should remove the package immediately and replace it with a trusted alternative. Regularly audit your dependencies for vulnerabilities.
Yes, Vulert can monitor your project for open-source vulnerabilities in real-time using just your package-lock.json file, without requiring code access.
