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

slamet-poke39 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166054: Malicious code in slamet-poke39 (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-poke39 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to interact with the npm registry, allowing developers to publish and manage their packages. However, slamet-poke39 has been identified as containing malicious code that compromises its integrity and the security of the npm ecosystem.

Vulnerability Detail

The vulnerability in slamet-poke39 originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores for token rewards by flooding the npm registry with derivative packages. The ramifications include potential abuse of the npm ecosystem, pollution of the registry, and risks to developers who may unknowingly use these compromised packages.

How To Fix

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

npm uninstall slamet-poke39

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 temporarily avoid using slamet-poke39 and any other packages associated with the tea.xyz token reward campaign until the issue is resolved. Regularly monitor your dependencies for any updates or patches.

Conclusion

The slamet-poke39 package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and floods the registry. Immediate action is required to remove this package and monitor for any updates or patches. Utilizing tools like Vulert can help maintain the security of your projects.

See every vulnerability recorded for slamet-poke39 →

Share this vulnerability

FAQ

slamet-poke39 is an npm package that has been identified as containing malicious code aimed at manipulating the npm registry.

The malicious code can alter your package.json file, remove private flags, and flood the npm registry with unwanted packages, potentially compromising your project's integrity.

You should uninstall slamet-poke39 immediately using the command 'npm uninstall slamet-poke39' and check your package-lock.json for any lingering references.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can check your application for vulnerabilities at the Vulert playground without any signup.

It is advisable to keep an eye on updates for slamet-poke39. If a patched version is released, updating to that version will be necessary to resolve the vulnerability.

How To Fix

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

npm uninstall slamet-poke39

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