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

slamet-poke80 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166102: Malicious code in slamet-poke80 (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-poke80 is an npm package that appears to be part of a larger scheme involving the tea.xyz token reward campaign. This package is designed to generate and publish derivative packages automatically, which can inflate developer reputation scores for token rewards. The malicious nature of this package poses a significant risk to developers and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in slamet-poke80 arises from its malicious code that modifies the package.json file to remove private flags and changes version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only compromises the security of the affected projects but also affects the overall reliability of the npm ecosystem.

How To Fix

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

npm uninstall slamet-poke80

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

Conclusion

The slamet-poke80 package poses a significant threat due to its malicious code that alters package configurations and floods the npm registry with harmful variants. Developers are urged to remove this package and monitor their projects for any vulnerabilities to maintain the integrity of their applications.

See every vulnerability recorded for slamet-poke80 →

Share this vulnerability

FAQ

slamet-poke80 is an npm package involved in a malicious scheme to inflate developer reputation scores through automated publishing of derivative packages.

The vulnerability can lead to the introduction of malicious code into your project, compromising its security and potentially affecting its functionality.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

You should uninstall slamet-poke80 immediately using 'npm uninstall slamet-poke80' and audit your project for any other affected packages.

Yes, tools like npm audit and Vulert can help you identify and manage vulnerabilities in your project's dependencies.

How To Fix

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

npm uninstall slamet-poke80

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