Malicious Code Detected in gcsearch Package: A Critical Security Alert

gcsearch Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21234: Malicious code in gcsearch (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 gcsearch package is an npm library designed to facilitate the search and retrieval of data from various sources. It is commonly used in JavaScript applications for its ease of integration and functionality. However, recent findings have revealed that this package contains malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability in the gcsearch package stems 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 issue was introduced in version 0 and affects all subsequent versions, making it imperative for users to take 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 gcsearch

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

Conclusion

The discovery of malicious code in the gcsearch package poses a serious threat to users and their applications. Immediate action is required to mitigate risks, including updating or removing the package. Stay informed about updates and consider using tools like Vulert to monitor for vulnerabilities in your software.

See every vulnerability recorded for gcsearch →

Share this vulnerability

FAQ

The gcsearch package is an npm library used for searching and retrieving data from various sources in JavaScript applications.

The malicious code can lead to unauthorized access and potential data breaches, compromising the security of applications that use this package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By checking your package-lock.json file, you can determine if your application is affected. Visit the Vulert playground at Vulert Scanner for a quick assessment without signup.

Currently, there is no patched version available. Users should monitor the package repository for updates and apply them as soon as they are released.

If removal is not an option, consider implementing additional security measures, such as code reviews and monitoring for suspicious activity, until a secure version is available.

How To Fix

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

npm uninstall gcsearch

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