Withdrawn Advisory Regarding grepleaks Package

grepleaks Updated 27 Jan 2026

Summary

27/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-530: Malicious code in grepleaks (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The grepleaks package is an npm module commonly used for detecting and managing secrets such as API keys, tokens, and other sensitive information within source code repositories. It is widely used in development and security workflows to help identify exposed credentials and prevent accidental leaks.

Vulnerability Detail

This advisory has been withdrawn. Earlier reports suggested that the grepleaks package contained malicious code capable of compromising systems where it was installed. However, after further investigation, it has been confirmed that grepleaks is not malware and does not contain malicious functionality. The advisory remains available only to preserve external references that may have linked to it. Users can continue using grepleaks as intended, ensuring they follow standard dependency management and security best practices.

How To Fix

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

npm uninstall grepleaks

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

No workaround is required. Since the advisory has been withdrawn, grepleaks can be used normally. Organizations should still maintain general security hygiene, including dependency scanning and monitoring tools.

Conclusion

The previously reported vulnerability claiming that the grepleaks package contained malicious code has been officially withdrawn. The package is not malware, and the advisory is kept only to maintain external references. Users should continue following standard dependency security practices and monitoring their software supply chain.

See every vulnerability recorded for grepleaks →

Share this vulnerability

FAQ

No. The advisory claiming grepleaks contained malicious code has been withdrawn. The package is not malware.

No. Since the advisory has been withdrawn and the package is not malicious, there is no need to remove it.

The advisory is maintained only to preserve external references that may already point to it, even though the vulnerability claim has been withdrawn.

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

Yes. Even though this advisory was withdrawn, it is still important to continuously monitor open-source dependencies for genuine security vulnerabilities.

How To Fix

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

npm uninstall grepleaks

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