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

slamet-poke23 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166037: Malicious code in slamet-poke23 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

slamet-poke23 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 has been known to flood the npm ecosystem with harmful packages. The primary functionality of slamet-poke23 is to serve as a conduit for automated scripts that generate and publish derivative packages, thereby inflating developer reputation scores for token rewards. Its attributes include the ability to modify package metadata and continuously republish variants, posing a significant risk to developers and users relying on npm packages.

Vulnerability Detail

The vulnerability in slamet-poke23 originates from its malicious design, which includes scripts that alter the package.json file by removing private flags and changing version numbers. This allows the package to generate random names, often themed around Indonesian culture, and republish itself to pollute the npm registry. The ramifications of this vulnerability include the potential for developers to unknowingly install compromised packages, leading to security breaches and loss of trust in the npm ecosystem. The technical aspects involve the use of autopublish scripts that automate the creation and distribution of these malicious packages.

How To Fix

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

npm uninstall slamet-poke23

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

Conclusion

The slamet-poke23 package poses a significant threat to the npm ecosystem due to its malicious design aimed at inflating developer reputation scores. It is crucial for developers to be vigilant and regularly audit their dependencies to avoid potential security breaches. By removing compromised packages and utilizing tools like Vulert, developers can enhance their security posture.

See every vulnerability recorded for slamet-poke23 →

Share this vulnerability

FAQ

slamet-poke23 is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated package publishing.

The vulnerability can lead to the installation of compromised packages, which may contain malicious code that can compromise your application's security.

You should remove the slamet-poke23 package from your project and check for any other affected packages. Consider using npm audit to identify vulnerabilities.

Yes, you can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.

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-poke23

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