Malicious Code Vulnerability in suharta-poke22: Exploitation of npm Registry

suharta-poke22 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166149: Malicious code in suharta-poke22 (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-poke22 package is part of a series of malicious packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by creating numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for token rewards, making it a significant concern for developers relying on npm for package management.

Vulnerability Detail

The vulnerability in suharta-poke22 stems from its inclusion in a malicious campaign that utilizes autopublish scripts to generate and publish numerous derivative packages. These scripts modify the package.json file by removing private flags, altering version numbers, and creating random package names. This not only pollutes the npm registry but also poses a risk of dependency confusion and potential exploitation by malicious actors, leading to compromised applications.

How To Fix

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

npm uninstall suharta-poke22

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 monitor your project for any unintended dependencies that may have been introduced by suharta-poke22. Regularly audit your npm packages using the command: npm audit to identify and address any vulnerabilities.

Conclusion

The suharta-poke22 package poses a significant risk due to its malicious nature and the potential for dependency confusion. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities in their applications. Regular audits and vigilance are essential to maintaining the security of your software.

See every vulnerability recorded for suharta-poke22 →

Share this vulnerability

FAQ

suharta-poke22 is a malicious npm package that is part of a campaign to inflate developer reputation scores through the creation of numerous derivative packages.

The vulnerability can lead to dependency confusion, allowing malicious actors to exploit your application by introducing compromised packages.

You should uninstall the package immediately using the command npm uninstall suharta-poke22 and check your package-lock.json for any references to it.

Yes, you can use Vulert to monitor and alert for open-source vulnerabilities in your software. It requires only the package-lock.json file for real-time alerts.

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

How To Fix

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

npm uninstall suharta-poke22

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