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

slamet-poke25 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166039: Malicious code in slamet-poke25 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

slamet-poke25 is an npm package that appears to be part of a broader malicious campaign targeting the npm registry. This package is designed to manipulate developer reputation scores through the automatic generation and publication of derivative packages. It modifies essential files and continuously republishes variants, leading to pollution of the npm registry.

Vulnerability Detail

The vulnerability in slamet-poke25 originates from its inclusion in a malicious campaign associated with the tea.xyz token reward initiative. The package contains scripts that automatically alter the package.json file by removing private flags and changing version numbers. It generates random package names, primarily themed around Indonesian culture, and repackages them to inflate developer reputation scores. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly use these tainted packages.

How To Fix

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

npm uninstall slamet-poke25

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 prevent the installation of slamet-poke25 by using npm's package-lock.json file to lock your dependencies. Ensure that your project does not include slamet-poke25 in its dependencies or devDependencies sections.

Conclusion

The slamet-poke25 package poses a significant threat to the npm ecosystem due to its malicious behavior aimed at manipulating developer reputation scores. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity of their applications.

See every vulnerability recorded for slamet-poke25 →

Share this vulnerability

FAQ

slamet-poke25 is an npm package that has been identified as part of a malicious campaign aimed at manipulating developer reputation scores.

The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project's dependencies.

You should remove slamet-poke25 from your project immediately and check for any other affected packages.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can check your application for vulnerabilities without any signup at the Vulert playground.

Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about the latest security advisories related to your packages.

How To Fix

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

npm uninstall slamet-poke25

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