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

slamet-poke6 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166079: Malicious code in slamet-poke6 (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-poke6 is an npm package that is part of a broader campaign involving the tea.xyz token reward system. This package is designed to facilitate the automatic generation and publication of derivative packages, which can lead to inflated developer reputation scores. The malicious nature of slamet-poke6 lies in its ability to modify package.json files, remove private flags, and generate random package names, thereby polluting the npm registry.

Vulnerability Detail

The vulnerability in slamet-poke6 originates from its involvement in a malicious campaign that aims to exploit the npm ecosystem. The package contains scripts that automatically republish variants of itself with altered metadata, including version numbers and package names. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly install these malicious packages, leading to potential security breaches and loss of sensitive data.

How To Fix

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

npm uninstall slamet-poke6

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-poke6 and any packages that depend on it. Additionally, consider using a package manager that provides enhanced security features or monitoring tools to detect malicious packages.

Conclusion

The slamet-poke6 package poses a significant threat to npm users due to its malicious behavior of modifying project files and republishing itself. It is crucial for developers to remove this package from their projects and utilize tools like Vulert for ongoing monitoring of vulnerabilities in their dependencies.

See every vulnerability recorded for slamet-poke6 →

Share this vulnerability

FAQ

slamet-poke6 is an npm package that is part of a malicious campaign aimed at exploiting the npm ecosystem for token rewards.

The package can modify your project's package.json file, remove private flags, and republish itself with altered metadata, potentially compromising your project's integrity.

You should uninstall slamet-poke6 immediately using the command 'npm uninstall slamet-poke6' and check your package-lock.json for any remaining references.

Yes, tools like Vulert can monitor your project for open-source vulnerabilities using just your package-lock.json file, alerting you in real-time.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall slamet-poke6

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