Malicious Code Injection in nasution-poke34 Package - npm Vulnerability
Summary
MAL-2025-162022: Malicious code in nasution-poke34 (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The nasution-poke34 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and deployment of applications by providing reusable code. However, it has been identified as part of a malicious campaign that exploits the npm registry, flooding it with derivative packages to manipulate developer reputation scores.
Vulnerability Detail
The vulnerability in the nasution-poke34 package stems from its association with a malicious campaign that modifies package.json files to remove private flags and change version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to significant security risks, including the potential for developers to unknowingly incorporate malicious code into their applications, compromising their integrity and security.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nasution-poke34If 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 measure, you can avoid using the nasution-poke34 package and any other packages that may be part of the malicious campaign. Regularly audit your package dependencies using tools like npm audit to identify and address vulnerabilities.
Conclusion
The nasution-poke34 package poses a significant security risk due to its malicious behavior of modifying package files and republishing variants to the npm registry. It is essential for developers to be vigilant about the packages they use and to regularly audit their dependencies to maintain application security.
See every vulnerability recorded for nasution-poke34 →
FAQ
The nasution-poke34 package is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.
You should uninstall the nasution-poke34 package immediately using the command npm uninstall nasution-poke34.
You can use tools like npm audit to regularly check for vulnerabilities in your installed packages.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. You can check your application against this vulnerability using the Vulert playground at Vulert Scanner without any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
