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

slamet-poke43 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166059: Malicious code in slamet-poke43 (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

slamet-poke43 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate token rewards through various automated scripts. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm ecosystem.

Vulnerability Detail

The vulnerability in slamet-poke43 originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only inflates developer reputation scores for token rewards but also pollutes the npm registry with potentially harmful packages, posing risks to developers and users who may unknowingly install these variants.

How To Fix

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

npm uninstall slamet-poke43

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, avoid using slamet-poke43 and any other packages associated with the tea.xyz token reward campaign. Regularly check your package-lock.json file for any dependencies that may have been inadvertently included.

Conclusion

The slamet-poke43 package poses a significant security risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package and monitor their dependencies for any vulnerabilities to maintain the integrity of their projects.

See every vulnerability recorded for slamet-poke43 →

Share this vulnerability

FAQ

slamet-poke43 is an npm package involved in a token reward campaign that has been identified to contain malicious code.

The vulnerability can lead to the installation of malicious packages, compromising your project's security and potentially affecting its functionality.

You should uninstall slamet-poke43 immediately using the command npm uninstall slamet-poke43.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

How To Fix

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

npm uninstall slamet-poke43

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