Malicious Code Injection in slamet-poke34: A Threat to npm Ecosystem
Summary
MAL-2025-166049: Malicious code in slamet-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
slamet-poke34 is an npm package that appears to be part of a broader malicious campaign targeting the npm ecosystem. It is designed to facilitate token reward schemes by generating and publishing derivative packages with randomized names. This behavior not only inflates developer reputation scores but also pollutes the npm registry, making it difficult for legitimate packages to be found.
Vulnerability Detail
The vulnerability in slamet-poke34 originates from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants. This behavior can lead to significant security risks, including the potential for dependency confusion and the introduction of untrusted code into projects that rely on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall slamet-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 slamet-poke34 and any packages that depend on it. Regularly audit your dependencies using tools like npm audit to identify and mitigate risks associated with malicious packages.
Conclusion
The slamet-poke34 package poses a significant threat to the npm ecosystem due to its malicious behavior. It is essential for developers to be vigilant and remove any instances of this package from their projects. Regular audits and monitoring can help mitigate risks associated with such vulnerabilities.
See every vulnerability recorded for slamet-poke34 →
FAQ
slamet-poke34 is an npm package involved in a malicious campaign that generates and publishes derivative packages to inflate developer reputation scores.
The vulnerability can introduce untrusted code into your project, leading to potential security risks and dependency confusion.
You should uninstall slamet-poke34 immediately using 'npm uninstall slamet-poke34' and check your package-lock.json for any references to it.
You can use tools like npm audit or services like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
