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

slamet-poke55 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166072: Malicious code in slamet-poke55 (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

slamet-poke55 is an npm package that is part of a broader campaign aimed at exploiting the npm registry. It is designed to facilitate token rewards for the tea.xyz protocol by generating and publishing numerous derivative packages. This behavior not only inflates developer reputation scores but also poses significant risks to users who may unknowingly install compromised packages.

Vulnerability Detail

The vulnerability in slamet-poke55 stems from its malicious code that 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 can lead to developers inadvertently installing malicious packages, compromising their applications and systems.

How To Fix

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

npm uninstall slamet-poke55

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 measure, you can avoid using slamet-poke55 and any packages that may depend on it. Regularly audit your package dependencies using tools like npm audit to identify and mitigate potential vulnerabilities.

Conclusion

The slamet-poke55 package poses a significant threat to npm users due to its malicious code designed to exploit the npm registry. It is essential to remove this package and regularly audit your dependencies to maintain the security of your applications.

See every vulnerability recorded for slamet-poke55 →

Share this vulnerability

FAQ

slamet-poke55 is an npm package that is part of a malicious campaign to exploit the npm registry for token rewards.

The vulnerability can lead to the installation of malicious code, which may compromise your application's security and integrity.

You should uninstall the package immediately using the command npm uninstall slamet-poke55 and audit your project for other potential vulnerabilities.

Regularly update your dependencies, use trusted packages, and utilize tools like npm audit to monitor for vulnerabilities.

Yes, Vulert can monitor your project for open-source vulnerabilities using just your package-lock.json file. You can check for vulnerabilities in real-time without any installation.

How To Fix

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

npm uninstall slamet-poke55

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