Malicious Code Injection in suharta-poke81: A Threat to npm Packages

suharta-poke81 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166214: Malicious code in suharta-poke81 (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

The package suharta-poke81 is part of the npm ecosystem, which is widely used for JavaScript package management. This package is linked to the tea.xyz token reward campaign, which has been associated with the proliferation of malicious packages designed to manipulate developer reputation scores. The vulnerability arises from the package's functionality, which includes scripts that automatically generate and publish derivative packages, leading to potential abuse of the npm registry.

Vulnerability Detail

The vulnerability in suharta-poke81 originates from its involvement in a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and generate random names, which can lead to the pollution of the npm registry. The ramifications include the potential for developers to unknowingly install compromised packages, which can introduce security risks and undermine the integrity of the npm ecosystem.

How To Fix

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

npm uninstall suharta-poke81

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, avoid using the suharta-poke81 package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your npm packages for vulnerabilities using tools like npm audit.

Conclusion

The suharta-poke81 package poses a significant security risk due to its involvement in a malicious campaign that manipulates the npm registry. It is crucial for developers to be vigilant, regularly audit their dependencies, and remove any compromised packages to maintain the integrity of their projects.

See every vulnerability recorded for suharta-poke81 →

Share this vulnerability

FAQ

suharta-poke81 is an npm package that is part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.

The vulnerability can lead to the installation of compromised packages, which may introduce security risks and affect the integrity of your project.

You should uninstall the package immediately using 'npm uninstall suharta-poke81' and audit your project for any other potentially compromised packages.

You can use tools like npm audit to check for vulnerabilities in your dependencies. Additionally, you can use Vulert to monitor and alert for open-source vulnerabilities in real-time.

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

How To Fix

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

npm uninstall suharta-poke81

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