Malicious Code Injection in slamet-poke54: A Threat to npm Ecosystem
Summary
MAL-2025-166071: Malicious code in slamet-poke54 (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-poke54 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 by flooding the registry with derivative packages. The malicious nature of slamet-poke54 lies in its ability to modify package metadata and republish variants, thereby compromising the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in slamet-poke54 originates from its design to execute autopublish scripts that alter the package.json file. These scripts remove private flags, change version numbers, and generate random package names, leading to the continuous republishing of malicious variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly install these compromised packages, potentially leading to further exploitation or data breaches.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall slamet-poke54
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, avoid using slamet-poke54 and any other packages associated with the tea.xyz token reward campaign. Instead, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The slamet-poke54 package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package metadata and republishing variants. It is essential for developers to remove this package from their projects and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for slamet-poke54 →
FAQ
slamet-poke54 is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores by flooding the npm registry with compromised packages.
The vulnerability can lead to the installation of malicious code that modifies your project's package.json, potentially compromising your application's integrity and security.
You should uninstall slamet-poke54 immediately using 'npm uninstall slamet-poke54' and check your project for any other compromised packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file. You can check your application for vulnerabilities using the Vulert playground at Vulert Scanner.
Yes, consider using other npm packages that provide similar functionality without the risks associated with slamet-poke54. Always verify the package's reputation and reviews before installation.