Malicious Code Injection in nasrul-poke47: A Threat to npm Packages
Summary
MAL-2025-161937: Malicious code in nasrul-poke47 (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-poke47' 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 function of such packages is to manipulate the npm ecosystem by generating and publishing derivative packages to inflate developer reputation scores.
Vulnerability Detail
The vulnerability in 'nasrul-poke47' stems from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which can lead to the pollution of the npm registry. This behavior is orchestrated through autopublish scripts that continuously republish variants of the package, posing a significant risk to developers and users relying on npm for secure package management.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nasrul-poke47If 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 'nasrul-poke47' package from your project by executing the command: 'npm uninstall nasrul-poke47'. This will prevent any malicious code from executing while you seek a secure alternative.
Conclusion
The 'nasrul-poke47' package poses a significant threat due to its malicious code designed to manipulate the npm ecosystem. It is crucial for developers to remain vigilant, update their packages regularly, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, the risks associated with such vulnerabilities can be mitigated.
See every vulnerability recorded for nasrul-poke47 →
FAQ
The main risk is the potential for malicious code to execute, which can compromise your project's integrity and security.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.
If immediate updates are not possible, consider removing the package from your project as a temporary measure.
Patches may be available depending on the latest updates from the package maintainers. Always check the npm registry for the latest version.
The malicious code can lead to the proliferation of derivative packages that clutter the npm registry, making it difficult for developers to find legitimate packages.
