Critical Malicious Code Vulnerability in godxxx Package

godxxx Updated 23 Sep 2026

Summary

23/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-16461: Malicious code in godxxx (npm). Affects godxxx versions 1.0.0. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The godxxx package is an npm module designed for various functionalities within JavaScript applications. However, it has been found to contain malicious code that poses significant security risks to users. The package is intended to facilitate development but has been compromised, making it a vector for attacks on applications that utilize it.

Vulnerability Detail

The vulnerability originates from the cdp_inject.js file, which is declared as the main module. This file unconditionally calls the main function at the top level, initiating a loop that polls for Chrome DevTools targets. It injects malicious scripts into every page, capturing sensitive information such as document body text and editor contents. This data is then base64-encoded and sent to a hardcoded HTTPS endpoint, compromising user privacy. Additionally, the module disables TLS certificate verification, allowing for potential man-in-the-middle attacks. A third-party API key is also embedded in the code, further exacerbating the security risks.

How To Fix

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

npm uninstall godxxx

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, users can avoid using the godxxx package until a patch is released. Additionally, consider implementing security measures such as monitoring network traffic for unusual activity and using tools like Vulert to detect vulnerabilities in your application.

Conclusion

The godxxx package contains a critical vulnerability that allows for the injection of malicious code, compromising user data and application security. Immediate action is required to update or remove the package to mitigate risks. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for godxxx →

Share this vulnerability

FAQ

The vulnerability involves malicious code that captures sensitive data and sends it to an external server, compromising user security.

You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.

If an immediate update is not possible, consider removing the package from your application and monitoring for any suspicious activity.

Yes, Vulert can monitor your project in real-time for open-source vulnerabilities using just your package-lock.json file.

Using the compromised package can lead to data breaches, unauthorized access to sensitive information, and potential exploitation of your application.

How To Fix

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

npm uninstall godxxx

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