Malicious Code Injection in slamet-poke19: A Threat to npm Packages

slamet-poke19 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166032: Malicious code in slamet-poke19 (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-poke19 is an npm package that appears to be part of a token reward campaign associated with the tea.xyz protocol. It is designed to facilitate the distribution of rewards through the npm ecosystem. However, this package has been identified as malicious, containing scripts that manipulate package metadata and publish unauthorized variants, which can compromise the integrity of the npm registry.

Vulnerability Detail

The vulnerability in slamet-poke19 originates from its inclusion in a campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. This can result in developers unknowingly using compromised packages, which may lead to security breaches and loss of trust in the npm ecosystem.

How To Fix

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

npm uninstall slamet-poke19

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-poke19 and any other packages associated with the tea.xyz token reward campaign. Regularly audit your project's dependencies to ensure that no malicious packages are included.

Conclusion

The slamet-poke19 package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry with compromised variants. It is essential to remove this package from your project and monitor your dependencies for any vulnerabilities to maintain the integrity of your software.

See every vulnerability recorded for slamet-poke19 →

Share this vulnerability

FAQ

slamet-poke19 is an npm package that has been identified as malicious, part of a campaign that floods the npm registry with compromised packages.

The malicious code modifies package metadata, potentially leading to the use of compromised packages and security vulnerabilities in your project.

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

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.

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

How To Fix

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

npm uninstall slamet-poke19

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