Malicious Code Injection in slamet-poke17: A Threat to npm Packages

slamet-poke17 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166030: Malicious code in slamet-poke17 (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-poke17 is an npm package that appears to be part of a token reward campaign associated with the tea.xyz protocol. This package is designed to interact with the npm registry, potentially inflating developer reputation scores through the automatic generation and publication of derivative packages. However, it has been identified as containing malicious code that compromises the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in slamet-poke17 originates from its malicious payload, which modifies the package.json file to remove private flags and alters 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 affects the reputation of legitimate developers but also poses a risk of dependency confusion and supply chain attacks.

How To Fix

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

npm uninstall slamet-poke17

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-poke17 in your project. If it is already included, remove it from your package.json and run npm install to clean up your dependencies.

Conclusion

The slamet-poke17 package poses a significant risk due to its malicious code that modifies package metadata and floods the npm registry. It is crucial for developers to remove this package from their projects and stay informed about potential updates or patches. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in real-time.

See every vulnerability recorded for slamet-poke17 →

Share this vulnerability

FAQ

slamet-poke17 is an npm package associated with a token reward campaign that has been identified to contain malicious code.

The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project's dependencies.

You should remove slamet-poke17 from your project and monitor for any updates or patches that may address the vulnerability.

Yes, you can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.

Long-term implications include potential dependency confusion, supply chain attacks, and damage to developer reputation within the npm ecosystem.

How To Fix

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

npm uninstall slamet-poke17

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