Malicious Code Detected in no6gg Package - Critical Vulnerability Alert

no6gg Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1801: Malicious code in no6gg (npm). Affects no6gg versions 1.0.0 – 1.0.9. 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 no6gg package is a JavaScript library available through npm, designed to facilitate various functionalities in Node.js applications. However, it has been identified as containing malicious code, which poses significant risks to users and their applications. This vulnerability affects multiple versions of the package, making it crucial for developers to be aware of its implications.

Vulnerability Detail

The vulnerability in the no6gg package arises from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The malicious nature of this vulnerability is confirmed by security researchers, emphasizing the need for immediate action to mitigate potential risks.

How To Fix

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

npm uninstall no6gg

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, users can remove the no6gg package from their project until a secure version is released. This can be done by running the following command: npm uninstall no6gg. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The no6gg package has been identified as containing malicious code, posing a significant risk to applications that utilize it. Immediate action is required to update or remove the package to safeguard your projects. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for no6gg →

Share this vulnerability

FAQ

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

The vulnerability involves malicious code embedded within the package, which can lead to security breaches and unauthorized access to applications.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in your software. Check your application using the Vulert playground at Vulert Scanner without any signup.

You should immediately update the no6gg package to the latest patched version or uninstall it until a secure version is available.

Detailed information can be found on the GitHub repository of the malicious packages, specifically at https://github.com/ossf/malicious-packages/blob/main/osv/malicious/npm/no6gg/MAL-2026-1801.json.

How To Fix

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

npm uninstall no6gg

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