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

slamet-poke103 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166006: Malicious code in slamet-poke103 (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

slamet-poke103 is an npm package that appears to be part of a malicious campaign targeting the npm registry. It is designed to manipulate package metadata and inflate developer reputation scores through automated publishing of derivative packages. This package is part of a broader scheme that exploits the npm ecosystem, potentially affecting developers and users relying on legitimate packages.

Vulnerability Detail

The vulnerability in slamet-poke103 originates from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and compromising the integrity of the ecosystem. The malicious payload can affect developers by inflating reputation scores through deceptive practices, ultimately undermining trust in the npm registry.

How To Fix

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

npm uninstall slamet-poke103

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 workaround, you can monitor your package dependencies using tools like Vulert. By utilizing Vulert's playground, you can check if your application is affected by this vulnerability without requiring any code access or installation. Visit https://vulert.com/scanner to use the service.

Conclusion

The slamet-poke103 package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to be vigilant and remove any affected packages to maintain the integrity of their projects. Utilizing tools like Vulert can help in monitoring for such vulnerabilities effectively.

See every vulnerability recorded for slamet-poke103 →

Share this vulnerability

FAQ

slamet-poke103 is an npm package involved in a malicious campaign that modifies package metadata to inflate developer reputation scores.

The vulnerability can lead to the pollution of the npm registry, compromising the integrity of your project's dependencies and potentially introducing malicious code.

You should uninstall slamet-poke103 immediately using 'npm uninstall slamet-poke103' and check for any dependencies that may rely on it.

Currently, there is no patched version available. The best course of action is to remove the package from your project.

You can use Vulert to monitor your project for open-source vulnerabilities in real-time by analyzing your package-lock.json file.

How To Fix

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

npm uninstall slamet-poke103

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