Malicious Code Injection in nasrul-poke44: A Threat to npm Ecosystem
Summary
MAL-2025-161934: Malicious code in nasrul-poke44 (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 'nasrul-poke44' 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. The primary functionality of such packages is to inflate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability in 'nasrul-poke44' 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 designed to create and republish derivative packages continuously, thereby compromising the integrity of the npm registry. The origin of this issue is linked to the tea.xyz token reward campaign, which employs these tactics to exploit the npm ecosystem for token rewards.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nasrul-poke44If 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 workaround, you can prevent the installation of this malicious package by using npm's audit feature to identify and remove vulnerable packages. Run the following command: 'npm audit fix' to automatically fix vulnerabilities in your project.
Conclusion
The nasrul-poke44 package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package management processes. It is essential to take immediate action by removing this package and regularly auditing your dependencies to maintain the security of your applications.
See every vulnerability recorded for nasrul-poke44 →
FAQ
The nasrul-poke44 vulnerability can lead to the pollution of the npm registry, compromising the integrity of package management and potentially affecting other projects that rely on npm.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit the Vulert playground at Vulert Scanner to check your application without any signup.
Yes, regularly audit your npm packages and remove any that are identified as malicious or vulnerable. Use 'npm audit' and 'npm audit fix' commands to help manage vulnerabilities.
If you have installed nasrul-poke44, it is recommended to uninstall it immediately using the command 'npm uninstall nasrul-poke44' to mitigate any risks.
Currently, there are no known patches for nasrul-poke44. The best course of action is to remove the package entirely from your project.
