Malicious Code Injection in slamet-poke65: A Threat to npm Ecosystem
Summary
MAL-2025-166085: Malicious code in slamet-poke65 (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-poke65 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of slamet-poke65 lies in its ability to modify package metadata and republish variants, thereby polluting the npm ecosystem.
Vulnerability Detail
The vulnerability in slamet-poke65 originates from its design to execute autopublish scripts that alter the package.json file. This includes removing private flags, changing version numbers, and generating random package names. The malicious payload allows the package to continuously republish variants, which can lead to reputation inflation for malicious actors and compromise the integrity of the npm registry. The potential ramifications include the proliferation of untrustworthy packages and increased difficulty for developers in identifying legitimate software.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall slamet-poke65If 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-poke65 and any other packages associated with the tea.xyz token reward campaign. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The slamet-poke65 package poses a significant threat to the npm ecosystem due to its malicious code that modifies package metadata and republish variants. Developers are urged to remove this package and monitor their projects for vulnerabilities using tools like Vulert to ensure the integrity of their software.
See every vulnerability recorded for slamet-poke65 →
FAQ
slamet-poke65 is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic publication of derivative packages.
The vulnerability allows malicious actors to modify package metadata and republish variants, which can lead to the introduction of untrustworthy packages into your project.
You should remove slamet-poke65 from your project and monitor for any updates or patches that may be released.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring any signup.
