Malicious Code Injection in slamet-poke62: A Threat to npm Users

slamet-poke62 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166082: Malicious code in slamet-poke62 (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-poke62 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 has been known to flood the npm ecosystem with harmful packages. The primary functionality of slamet-poke62 is to serve as a tool for developers, but its malicious nature compromises its integrity and poses significant risks to users.

Vulnerability Detail

The vulnerability in slamet-poke62 originates from its design as part of a broader malicious strategy to inflate developer reputation scores through the automatic generation and publication of derivative packages. This package modifies the package.json file to remove private flags, alters version numbers, and creates random package names, leading to pollution of the npm registry. The ramifications include potential exposure of sensitive data, unauthorized access to systems, and a compromised development environment.

How To Fix

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

npm uninstall slamet-poke62

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, users can avoid using slamet-poke62 and any other packages associated with the tea.xyz token reward campaign. Additionally, consider using the following command to uninstall the package: npm uninstall slamet-poke62.

Conclusion

The slamet-poke62 package poses a significant threat to npm users due to its malicious code designed to manipulate package metadata and inflate developer reputation scores. Immediate action is required to remove this package and safeguard your projects from potential risks. Utilizing tools like Vulert can help maintain the security of your software dependencies.

See every vulnerability recorded for slamet-poke62 →

Share this vulnerability

FAQ

slamet-poke62 is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of harmful packages.

The vulnerability can lead to unauthorized modifications of your project's package.json file, potentially exposing sensitive data and compromising your development environment.

You should uninstall slamet-poke62 immediately and check for any other malicious packages that may have been installed as part of the same campaign.

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

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

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-poke62

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