Malicious Code Injection in suharta-poke35: A Threat to npm Ecosystem

suharta-poke35 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

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

The suharta-poke35 package is part of a series of malicious npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. The primary function of suharta-poke35 is to inflate developer reputation scores through automated scripts, which can lead to significant pollution of the npm ecosystem.

Vulnerability Detail

The vulnerability in suharta-poke35 stems from its inclusion in a malicious campaign that modifies package.json files to remove private flags and change version numbers. This allows the package to continuously republish variants with random names, thereby compromising the integrity of the npm registry. The malicious payload can lead to unauthorized access and manipulation of projects that depend on this package, potentially causing widespread issues in software development.

How To Fix

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

npm uninstall suharta-poke35

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 prevent the installation of the suharta-poke35 package by using npm's package-lock.json to monitor your dependencies. If you suspect that your project may have been affected, consider using the following command to audit your project for vulnerabilities: 'npm audit'.

Conclusion

The suharta-poke35 package poses a significant threat to the npm ecosystem due to its malicious nature and ability to manipulate package dependencies. It is essential for developers to remain vigilant, regularly audit their projects, and utilize tools like Vulert to ensure their applications are secure from such vulnerabilities.

See every vulnerability recorded for suharta-poke35 →

Share this vulnerability

FAQ

suharta-poke35 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing of derivative packages.

The vulnerability can lead to unauthorized modifications in your project's dependencies, potentially compromising the security and integrity of your application.

You can use the Vulert platform to monitor your package-lock.json for vulnerabilities. Visit Vulert Scanner to check if your application is affected without requiring any signup.

You should immediately uninstall the package using 'npm uninstall suharta-poke35' and review your project dependencies for any other malicious packages.

Regularly audit your project dependencies using 'npm audit', keep your packages updated, and utilize tools like Vulert to monitor for open-source vulnerabilities.

How To Fix

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

npm uninstall suharta-poke35

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