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

slamet-poke18 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166031: Malicious code in slamet-poke18 (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-poke18 is an npm package that is part of the tea.xyz token reward campaign, which has been associated with a series of malicious packages flooding the npm registry. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with random names. The presence of such malicious packages poses a significant risk to developers and users relying on npm for package management.

Vulnerability Detail

The vulnerability in slamet-poke18 originates from its inclusion in a malicious campaign that employs scripts to modify package.json files. This manipulation removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The ramifications include compromised developer reputations, potential security risks for applications using these packages, and a degraded npm ecosystem.

How To Fix

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

npm uninstall slamet-poke18

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 workaround, you can remove the slamet-poke18 package from your project by executing the following command in your terminal: npm uninstall slamet-poke18. This will prevent any malicious code from executing in your application.

Conclusion

The slamet-poke18 package poses a significant risk due to its malicious code designed to manipulate npm package management. It is crucial for developers to be aware of such vulnerabilities and take immediate action to secure their applications by removing affected packages and monitoring for future threats.

See every vulnerability recorded for slamet-poke18 →

Share this vulnerability

FAQ

slamet-poke18 is an npm package associated with a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages.

The vulnerability can lead to the modification of your package.json file, potentially compromising your application's integrity and security.

You should uninstall slamet-poke18 immediately to mitigate any risks associated with the malicious code.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software by analyzing your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

npm uninstall slamet-poke18

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