Malicious Code Injection in slamet-poke10 Package: npm Vulnerability Overview

slamet-poke10 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166002: Malicious code in slamet-poke10 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The slamet-poke10 package is part of the npm ecosystem, primarily used for JavaScript development. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The package's functionality is compromised by the presence of scripts designed to manipulate package metadata and publish unauthorized derivatives, posing a significant risk to developers and users alike.

Vulnerability Detail

The vulnerability in slamet-poke10 originates from its malicious code, 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 clutter the npm registry. This behavior not only inflates developer reputation scores for token rewards but also compromises the integrity of the npm ecosystem, potentially leading to security breaches and misuse of developer resources.

How To Fix

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

npm uninstall slamet-poke10

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 remove the slamet-poke10 package from your project by executing the following command: npm uninstall slamet-poke10. This will prevent any malicious code from executing while you seek a secure alternative.

Conclusion

The slamet-poke10 package poses a significant security risk due to its malicious code designed to manipulate npm package metadata. It is crucial for developers to update or remove this package to protect their applications. Utilizing tools like Vulert can help monitor for such vulnerabilities effectively.

See every vulnerability recorded for slamet-poke10 →

Share this vulnerability

FAQ

slamet-poke10 is an npm package that has been identified as containing malicious code aimed at manipulating package metadata and inflating developer reputation scores.

The vulnerability can lead to unauthorized changes in your project's dependencies, potentially allowing malicious code to execute and compromising your application's security.

Yes, you can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.

If you cannot update the package right away, consider uninstalling it to mitigate risks until a secure version is available.

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

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