Malicious Code Injection in suharta-poke82 Package - npm Vulnerability

suharta-poke82 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

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

The suharta-poke82 package is part of the npm ecosystem, often used in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to manipulate developer reputation scores through automated publishing scripts, which can lead to significant issues in the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability originates from the suharta-poke82 package, which contains malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores fraudulently and pollute the npm registry with numerous derivative packages. The ramifications include potential security risks for developers who unknowingly use these packages, as they may introduce vulnerabilities or malicious behavior into their applications.

How To Fix

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

npm uninstall suharta-poke82

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 avoid using the suharta-poke82 package altogether. If it is already in use, consider replacing it with a trusted alternative or removing it from your dependencies. Additionally, you can monitor your package-lock.json file for any unauthorized changes.

Conclusion

The suharta-poke82 package poses a significant risk due to its malicious code designed to manipulate npm's ecosystem. It is crucial for developers to be vigilant about the packages they use and to take immediate action to remove any compromised packages. Utilizing tools like Vulert can help in monitoring and ensuring the security of your dependencies.

See every vulnerability recorded for suharta-poke82 →

Share this vulnerability

FAQ

suharta-poke82 is an npm package that has been identified as part of a malicious campaign to manipulate developer reputation scores through automated publishing.

Using the suharta-poke82 package can introduce security risks and potentially compromise your project's integrity by allowing malicious code to execute.

You should remove the suharta-poke82 package from your project and check for any unauthorized changes in your package.json and package-lock.json files.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json. You can check your application for vulnerabilities at the Vulert playground without any signup.

Regularly audit your dependencies using tools like npm audit, and keep your packages updated to the latest secure versions.

How To Fix

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

npm uninstall suharta-poke82

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