Malicious Code Detected in girard Package - Security Alert

girard Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21448: Malicious code in girard (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The girard package is an npm library designed for specific functionalities within JavaScript applications. It is utilized by developers for various tasks, but its recent discovery of malicious code poses significant risks. This vulnerability can compromise the security of applications that rely on this package, making it crucial for users to be aware and take action.

Vulnerability Detail

The girard package has been identified to contain malicious code, which can lead to unauthorized access, data breaches, or other harmful actions within applications that utilize it. This vulnerability originated from the package itself, and it affects all versions starting from 0. The implications of this vulnerability are severe, as it can be exploited by attackers to manipulate or steal sensitive information.

How To Fix

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

npm uninstall girard

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, consider removing the girard package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall girard'. This will help mitigate the risk of exploitation while you await a fix.

Conclusion

The discovery of malicious code in the girard package poses a significant threat to applications that utilize it. It is crucial for developers to take immediate action by updating or removing the package to safeguard their projects. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for girard →

Share this vulnerability

FAQ

The girard package is an npm library used for various functionalities in JavaScript applications, but its specific use cases can vary depending on the project.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By simply using your package-lock.json file, you can check if your application is affected without needing to install any additional tools.

If an immediate update is not possible, consider removing the girard package from your project as a temporary measure to reduce risk.

Detailed information about the vulnerability can be found on the GitHub repository of the malicious packages project, specifically at the URL provided in the vulnerability details.

Yes, you can use Vulert's playground to monitor your dependencies for vulnerabilities. You can access it at Vulert Scanner without signing up.

How To Fix

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

npm uninstall girard

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