Malicious Code Injection in slamet-poke41: A Threat to npm Packages
Summary
MAL-2025-166057: Malicious code in slamet-poke41 (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-poke41 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 this package compromises the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in slamet-poke41 stems from its inclusion in a series of malicious packages that contain scripts designed to manipulate package metadata. Specifically, the malicious payload alters the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly install these compromised packages, leading to potential security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall slamet-poke41If 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-poke41 and any other packages associated with the tea.xyz token reward campaign. Regularly audit your package.json and package-lock.json files to identify and remove any suspicious packages.
Conclusion
The slamet-poke41 package poses a significant risk due to its malicious code that alters package metadata and pollutes the npm registry. It is essential for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to safeguard their applications against such vulnerabilities.
See every vulnerability recorded for slamet-poke41 →
FAQ
slamet-poke41 is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the installation of compromised packages, which may modify your application's behavior, expose sensitive data, or introduce additional security risks.
You should immediately uninstall slamet-poke41 using the command npm uninstall slamet-poke41 and audit your project for any other potentially malicious packages.
Regularly update your dependencies, use trusted packages, and consider using tools like Vulert to monitor your project for open-source vulnerabilities.
Vulert is a tool that monitors and alerts you in real-time for open-source vulnerabilities in your software using just the package-lock.json file. You can check if your application is affected by visiting the Vulert playground at Vulert Scanner.
