Malicious Code Injection in slamet-poke95: A Threat to npm Ecosystem

slamet-poke95 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166118: Malicious code in slamet-poke95 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

slamet-poke95 is an npm package that is part of a broader campaign to exploit the npm registry. It is designed to facilitate the distribution of malicious code by automatically generating and publishing derivative packages. This package, like others in the campaign, aims to inflate developer reputation scores through deceptive practices.

Vulnerability Detail

The vulnerability originates from the malicious intent behind the slamet-poke95 package, which is part of a token reward scheme that floods the npm registry with spam packages. The malicious payload alters the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior can lead to the pollution of the npm registry, potentially compromising the integrity of other packages and affecting developers relying on npm for legitimate software.

How To Fix

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

npm uninstall slamet-poke95

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, avoid using the slamet-poke95 package and monitor your project for any dependencies that may inadvertently include it. Regularly audit your dependencies using tools like npm audit or Vulert to ensure no malicious packages are present.

Conclusion

The slamet-poke95 package poses a significant threat to the npm ecosystem due to its malicious behavior aimed at inflating developer reputation scores. It is crucial for developers to be vigilant, remove any affected packages, and utilize tools like Vulert to monitor for vulnerabilities in their projects.

See every vulnerability recorded for slamet-poke95 →

Share this vulnerability

FAQ

slamet-poke95 is an npm package involved in a malicious campaign to inflate developer reputation scores through the automatic generation of spam packages.

The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of other packages and affecting developers who rely on npm for legitimate software.

You should uninstall the slamet-poke95 package immediately using the command npm uninstall slamet-poke95 and check your package-lock.json for any references to it.

You can use tools like npm audit or Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall slamet-poke95

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