Critical Malicious Code Vulnerability in npm Package 3gr841

3gr841 Updated 19 Oct 2026

Summary

19/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17946: Malicious code in 3gr841 (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 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 npm package 3gr841 is a JavaScript library that is typically used in Node.js applications for various functionalities. However, this package has been identified as containing malicious code that compromises the security of any system it is installed on. Users of this package are at risk of having their secrets and keys exposed, leading to potential data breaches and unauthorized access.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the 3gr841 package. This code can fully compromise any computer that has the package installed, allowing an outside entity to gain control over the system. The ramifications of this vulnerability are severe, as it can lead to the theft of sensitive information and unauthorized actions being performed on the affected system. The vulnerability is classified under CWE-506, which indicates that the product contains code that appears to be malicious in nature.

How To Fix

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

npm uninstall 3gr841

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 to mitigate the risks posed by this malicious package. The only recommended action is to uninstall the package and secure your environment.

Conclusion

The 3gr841 npm package has been identified as containing malicious code that compromises the security of any system it is installed on. Users are advised to uninstall the package immediately and rotate any sensitive information. Regular monitoring with tools like Vulert can help prevent future vulnerabilities.

See every vulnerability recorded for 3gr841 →

Share this vulnerability

FAQ

Immediately uninstall the package using npm uninstall 3gr841 and rotate any secrets or keys stored on the affected system.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.

Keeping 3gr841 installed poses significant risks, including unauthorized access to your system, data breaches, and potential loss of sensitive information.

Currently, there is no patched version of the 3gr841 package available. The only solution is to uninstall it.

Vulert uses the package-lock.json file to monitor and alert in real-time for open-source vulnerabilities in your software, helping you maintain a secure environment.

How To Fix

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

npm uninstall 3gr841

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