Malicious Code Injection in slamet-poke11: A Threat to npm Users
Summary
MAL-2025-166013: Malicious code in slamet-poke11 (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
slamet-poke11 is an npm package that appears to be part of a larger campaign aimed at exploiting the npm registry. This package, like others in the campaign, is designed to manipulate developer reputation scores through the automatic generation and publication of derivative packages. Its primary functionality is to serve as a token reward mechanism, but it has been compromised to include malicious scripts that can harm users and the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in slamet-poke11 originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these compromised packages, leading to potential security breaches and loss of trust in the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall slamet-poke11If 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 an immediate workaround, consider removing the slamet-poke11 package from your project if it is not essential. You can do this by executing: npm uninstall slamet-poke11. Additionally, monitor your package-lock.json file for any unexpected changes or additions.
Conclusion
The slamet-poke11 package poses a significant threat due to its malicious code injection capabilities. Users are urged to take immediate action by updating or removing the package and utilizing tools like Vulert to monitor for vulnerabilities in their projects. Awareness and proactive measures are essential to maintaining the security of the npm ecosystem.
See every vulnerability recorded for slamet-poke11 →
FAQ
slamet-poke11 is an npm package that has been identified as part of a malicious campaign targeting the npm registry.
The vulnerability can lead to the introduction of malicious code into your project, potentially compromising security and integrity.
You should uninstall the package immediately and check for any other affected packages in your project.
You can use Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.
Regularly update your dependencies, use tools like Vulert for monitoring, and review package sources before installation to mitigate risks.
