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

slamet-poke51 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166068: Malicious code in slamet-poke51 (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

slamet-poke51 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to interact with the npm registry, allowing developers to publish and manage their packages. However, it has been identified as malicious, containing scripts that manipulate package metadata and publish derivative packages to inflate developer reputation scores.

Vulnerability Detail

The vulnerability in slamet-poke51 originates from its inclusion in a campaign that floods the npm registry with malicious packages. It modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. This can result in developers unknowingly using compromised packages, potentially exposing their applications to further security risks.

How To Fix

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

npm uninstall slamet-poke51

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 avoid using slamet-poke51 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 risks from malicious packages.

Conclusion

The slamet-poke51 package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to remove this package and regularly audit their dependencies to maintain the security of their applications. Utilizing tools like Vulert can help in monitoring for vulnerabilities effectively.

See every vulnerability recorded for slamet-poke51 →

Share this vulnerability

FAQ

slamet-poke51 is an npm package that has been identified as malicious, designed to manipulate package metadata and publish derivative packages.

The vulnerability can lead to the use of compromised packages, which may introduce security risks and affect the integrity of your application.

You should uninstall slamet-poke51 immediately using 'npm uninstall slamet-poke51' and check for any other affected packages.

You can use tools like npm audit to scan your project for vulnerabilities. Additionally, Vulert can monitor your package-lock.json for real-time alerts on open-source vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall slamet-poke51

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