Malicious Code Injection in slamet-poke35: A Threat to npm Packages
Summary
MAL-2025-166050: Malicious code in slamet-poke35 (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-poke35 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-poke35 lies in its ability to modify package metadata and republish itself under various names, thereby compromising the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in slamet-poke35 originates from its design to execute autopublish scripts that alter the package.json file. It removes private flags, changes version numbers, and generates random package names, which leads to the pollution of the npm registry. This behavior can have severe ramifications, including the potential for developers to unknowingly install compromised packages, leading to security breaches and loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall slamet-poke35If 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-poke35 by using npm's package-lock.json to monitor dependencies. You can also manually check your package.json for any references to slamet-poke35 and remove them.
Conclusion
The slamet-poke35 package poses a significant threat to the integrity of the npm ecosystem due to its malicious behavior. It is crucial for developers to be vigilant and take immediate action to remove this package from their projects. Utilizing tools like Vulert can help in identifying and mitigating such vulnerabilities in the future.
See every vulnerability recorded for slamet-poke35 →
FAQ
slamet-poke35 is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the creation of derivative packages.
The presence of slamet-poke35 in your project can lead to the modification of your package.json file and the potential installation of compromised packages, which can introduce security vulnerabilities.
You can use Vulert, which monitors open-source vulnerabilities in your software. By analyzing your package-lock.json file, Vulert can alert you to any vulnerabilities, including those from slamet-poke35.
You should uninstall slamet-poke35 immediately using 'npm uninstall slamet-poke35' and review your project for any dependencies that may rely on it.
Regularly monitor your dependencies using tools like Vulert and keep your packages updated to their latest versions to mitigate the risk of vulnerabilities.
