Malicious Code Injection in siregar-poke40: A Threat to npm Users
Summary
MAL-2025-165959: Malicious code in siregar-poke40 (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
siregar-poke40 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is designed to manipulate the npm ecosystem by generating and publishing derivative packages with randomized names, aiming to inflate developer reputation scores for token rewards. The malicious nature of this package poses significant risks to developers and users relying on npm for package management.
Vulnerability Detail
The vulnerability in siregar-poke40 originates from its inclusion in a campaign that floods the npm registry with malicious packages. The package contains scripts that modify the package.json file to remove private flags, alter version numbers, and create random package names. This behavior leads to the continuous republishing of these variants, polluting the npm registry and potentially compromising the integrity of other packages and applications that depend on it.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall siregar-poke40If 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 siregar-poke40 package and any other packages that may have been published as part of this malicious campaign. Monitor your package-lock.json file for any unexpected changes or additions that may indicate the presence of malicious packages.
Conclusion
The siregar-poke40 package poses a significant threat to the npm ecosystem due to its malicious behavior. It is essential for developers to be vigilant and take immediate action to remove any affected packages and monitor their dependencies 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 siregar-poke40 →
FAQ
siregar-poke40 is an npm package identified as part of a malicious campaign that floods the npm registry with harmful packages.
The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your project and its dependencies.
You should uninstall the siregar-poke40 package immediately using 'npm uninstall siregar-poke40' and check your project for any other malicious packages.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
