Malicious Code Injection in slamet-poke20: A Threat to npm Users
Summary
MAL-2025-166034: Malicious code in slamet-poke20 (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-poke20 is an npm package that is part of a broader campaign aimed at manipulating the npm registry for token rewards. This package, like others in the campaign, is designed to inflate developer reputation scores through the automatic generation and publication of derivative packages. Its functionality is compromised by malicious scripts that alter its metadata and behavior, making it a target for developers unaware of its risks.
Vulnerability Detail
The vulnerability in slamet-poke20 stems from its association with a malicious campaign that modifies the package.json file to remove private flags, changes version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which employs autopublish scripts to automate the malicious activities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall slamet-poke20
If 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 prevent the installation of slamet-poke20 by adding it to your project's .npmrc file with the following line: 'ignore-scripts=true'. This will disable any scripts that may run during installation, but it is recommended to remove the package entirely.
Conclusion
The slamet-poke20 package presents a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to be vigilant and remove any affected packages to maintain the integrity of their projects. Utilizing tools like Vulert can help in monitoring and identifying such vulnerabilities in real-time.
See every vulnerability recorded for slamet-poke20 →
FAQ
slamet-poke20 is an npm package that is part of a malicious campaign aimed at manipulating the npm registry for token rewards.
The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project by introducing malicious code.
You should uninstall slamet-poke20 immediately and check for any other potentially affected 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 signing up.