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

slamet-poke94 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166117: Malicious code in slamet-poke94 (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-poke94 is an npm package that is part of a larger campaign exploiting the npm registry. It is designed to facilitate the tea.xyz token reward system, which has been associated with malicious activities. This package, like others in the campaign, is intended to inflate developer reputation scores by automatically generating and publishing derivative packages with altered names and metadata.

Vulnerability Detail

The vulnerability in slamet-poke94 originates from its design to include autopublish scripts that modify the package.json file. These modifications remove private flags, alter version numbers, and generate random package names, leading to pollution of the npm registry. This behavior can result in developers unknowingly installing malicious packages, compromising the integrity of their applications and potentially leading to security breaches.

How To Fix

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

npm uninstall slamet-poke94

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

Conclusion

The slamet-poke94 package poses a significant threat to the npm ecosystem due to its malicious behavior aimed at inflating developer reputation scores. It is crucial for developers to be vigilant and remove such packages from their projects to maintain the security of their applications.

See every vulnerability recorded for slamet-poke94 →

Share this vulnerability

FAQ

slamet-poke94 is an npm package involved in a malicious campaign to inflate developer reputation scores by publishing derivative packages.

The vulnerability can lead to the installation of malicious packages, compromising your application's security and integrity.

You should uninstall slamet-poke94 immediately and check for any dependencies that may rely on it.

You can use tools like npm audit or Vulert, which monitors your package-lock.json for vulnerabilities in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

npm uninstall slamet-poke94

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