Malicious Code Injection in nasution-poke50: A Threat to npm Users
Summary
MAL-2025-162040: Malicious code in nasution-poke50 (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 nasution-poke50 is part of a series of malicious npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior not only clutters the npm registry but also poses significant security risks to users who may inadvertently install these compromised packages.
Vulnerability Detail
The vulnerability in nasution-poke50 stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior allows the package to continuously republish variants, polluting the npm registry and potentially leading to the installation of compromised software by unsuspecting developers. The origin of this vulnerability is linked to a broader campaign aimed at exploiting npm's publishing mechanisms for token rewards.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nasution-poke50If 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 nasution-poke50 package and monitor your project for any dependencies that may inadvertently include it. Regularly audit your package-lock.json file to identify and remove any malicious packages.
Conclusion
The nasution-poke50 package represents a significant security threat within the npm ecosystem, stemming from a malicious campaign aimed at exploiting npm's publishing features. By understanding the nature of this vulnerability and taking proactive steps to remove affected packages, developers can protect their projects from potential harm.
See every vulnerability recorded for nasution-poke50 →
FAQ
nasution-poke50 is a malicious npm package that is part of a campaign to inflate developer reputation scores by flooding the npm registry with compromised packages.
If you have installed nasution-poke50, your project may be at risk of using compromised code, which can lead to security breaches and instability.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected.
Immediately uninstall the nasution-poke50 package using the command 'npm uninstall nasution-poke50' and review your dependencies for any other malicious packages.
Regularly audit your dependencies, use trusted packages, and keep your software updated to minimize the risk of vulnerabilities.
