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

slamet-poke15 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166028: Malicious code in slamet-poke15 (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-poke15 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 through the automatic generation and publication of derivative packages. The package's functionality is compromised by malicious scripts that alter its metadata and behavior.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the slamet-poke15 package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The origin of this issue is linked to a broader campaign that floods the npm registry with such malicious packages, posing a risk to developers and users by polluting the ecosystem and potentially leading to the installation of harmful software.

How To Fix

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

npm uninstall slamet-poke15

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 measure, avoid using slamet-poke15 and monitor your project's dependencies for any signs of malicious activity. You can also utilize tools like Vulert to monitor your package-lock.json for vulnerabilities. For example, you can check if your application is affected by visiting the Vulert playground at https://vulert.com/scanner.

Conclusion

The slamet-poke15 package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and behavior. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities. Staying informed and proactive is essential in maintaining a secure development environment.

See every vulnerability recorded for slamet-poke15 →

Share this vulnerability

FAQ

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

The malicious code modifies your package.json file, potentially leading to the installation of harmful software and polluting the npm registry with unwanted packages.

You should uninstall slamet-poke15 immediately using 'npm uninstall slamet-poke15' and monitor your project for any further vulnerabilities.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check your application at Vulert Scanner.

Currently, there are no patches available for slamet-poke15. The best course of action is to remove the package from your project.

How To Fix

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

npm uninstall slamet-poke15

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