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

suharta-poke101 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166126: Malicious code in suharta-poke101 (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

suharta-poke101 is an npm package that appears to be part of a larger campaign aimed at exploiting the npm registry. This package, like others in the campaign, is designed to manipulate developer reputation scores through the automatic generation and publication of derivative packages. It is essential for developers to understand the implications of using such packages, as they can lead to significant security risks and pollution of the npm ecosystem.

Vulnerability Detail

The vulnerability in suharta-poke101 stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is part of a broader scheme to inflate developer reputation scores for token rewards associated with the tea.xyz protocol. The continuous republishing of these variants can lead to a polluted npm registry, making it difficult for developers to find legitimate packages and increasing the risk of dependency confusion attacks.

How To Fix

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

npm uninstall suharta-poke101

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 measure, avoid using the suharta-poke101 package and consider using alternative packages that provide similar functionality without the associated risks. Always verify the integrity and source of packages before installation.

Conclusion

The suharta-poke101 package poses a significant threat to the npm ecosystem due to its malicious code aimed at manipulating developer reputation scores. It is crucial for developers to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help ensure that your applications remain secure.

See every vulnerability recorded for suharta-poke101 →

Share this vulnerability

FAQ

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

Using suharta-poke101 can lead to security risks, including dependency confusion and pollution of the npm registry, making it harder to find legitimate packages.

You should uninstall the suharta-poke101 package immediately using 'npm uninstall suharta-poke101' and check your project for any other potentially malicious packages.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground at Vulert Scanner.

Yes, consider using well-established packages that provide similar functionality but have a strong reputation and community support.

How To Fix

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

npm uninstall suharta-poke101

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