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

slamet-poke1 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166001: Malicious code in slamet-poke1 (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-poke1 is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem. This package is associated with the tea.xyz token reward scheme, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of slamet-poke1 lies in its ability to modify essential files and publish harmful variants, thereby compromising the integrity of the npm registry.

Vulnerability Detail

The vulnerability in slamet-poke1 originates from its design to include autopublish scripts that remove private flags from package.json, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of these malicious variants, which can pollute the npm registry and potentially expose users to further security risks. The ramifications include loss of trust in the npm ecosystem, potential data breaches, and the risk of executing malicious code unknowingly.

How To Fix

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

npm uninstall slamet-poke1

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-poke1 and any other packages associated with the tea.xyz token reward campaign. Regularly audit your dependencies using tools like npm audit to identify and mitigate potential vulnerabilities.

Conclusion

The slamet-poke1 package poses a significant threat to the npm ecosystem due to its malicious behavior. It is essential for developers to be vigilant, regularly audit their dependencies, and take immediate action to remove any affected packages to maintain the security of their projects.

See every vulnerability recorded for slamet-poke1 →

Share this vulnerability

FAQ

slamet-poke1 is an npm package linked to a malicious campaign that aims to inflate developer reputation scores through the automatic generation of harmful packages.

The package modifies critical files and can republish malicious variants, potentially compromising your project's security and the integrity of the npm registry.

You should uninstall slamet-poke1 immediately using the command 'npm uninstall slamet-poke1' and check for any other affected packages.

You can use tools like npm audit or services like 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-poke1

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