Critical Malicious Code Vulnerability in kinggupong Package

kinggupong Updated 13 Mar 2026

Summary

12/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1369: Malicious code in kinggupong (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 kinggupong package is a Node.js library available through npm, designed for various functionalities within JavaScript applications. However, it has been identified as containing malicious code that compromises the security of any system where it is installed. This vulnerability poses a significant risk to developers and users alike, as it can lead to unauthorized access and control over affected systems.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the kinggupong package. Any system running this package is considered fully compromised, with all stored secrets and keys at risk. The malicious code can allow an external entity to gain full control over the affected computer, making it imperative for users to act swiftly to mitigate the risks associated with this vulnerability.

How To Fix

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

npm uninstall kinggupong

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

There are no effective workarounds for this vulnerability. The only recommended action is to uninstall the kinggupong package and secure your system by rotating any compromised credentials.

Conclusion

The kinggupong package has been identified as containing malicious code that poses a significant risk to any system where it is installed. Immediate action is required to uninstall the package and secure any compromised credentials. Users are encouraged to utilize tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for kinggupong →

Share this vulnerability

FAQ

kinggupong is a Node.js library available on npm, used for various functionalities in JavaScript applications.

A compromised system means that an external entity may have gained unauthorized access and control over your computer, potentially leading to data theft or further malicious activities.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in your software. By simply uploading your package-lock.json file, you can check for vulnerabilities without needing to install any software.

You should rotate all secrets and keys stored on the compromised system immediately from a different, secure computer to prevent unauthorized access.

No, there is currently no patched version available for the kinggupong package. The only solution is to uninstall it.

How To Fix

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

npm uninstall kinggupong

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