Malicious Code Injection in slamet-poke24: A Threat to npm Ecosystem

slamet-poke24 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166038: Malicious code in slamet-poke24 (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

slamet-poke24 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate interactions within the npm ecosystem, but it has been identified as containing malicious code that can compromise the integrity of the npm registry. The package is known for generating and publishing derivative packages with randomized names, which can lead to reputation inflation for developers involved in the tea protocol.

Vulnerability Detail

The vulnerability in slamet-poke24 originates from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only pollutes the npm registry but also poses a risk to developers by potentially introducing malicious code into their projects. The continuous republishing of these variants can lead to significant security risks and undermine 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-poke24

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 avoid using slamet-poke24 and any other packages associated with the tea.xyz token reward campaign. Regularly audit your project's dependencies using tools like npm audit to identify and mitigate potential vulnerabilities.

Conclusion

The slamet-poke24 package poses a significant security risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package from their projects and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your applications.

See every vulnerability recorded for slamet-poke24 →

Share this vulnerability

FAQ

slamet-poke24 is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the creation of derivative packages.

The vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.

You should uninstall slamet-poke24 immediately using the command npm uninstall slamet-poke24 and audit your project for any other vulnerabilities.

Yes, you can use Vulert to monitor and alert in real-time for open-source vulnerabilities in your software. It requires only the package-lock.json file for analysis.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall slamet-poke24

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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback