Critical Malicious Code Vulnerability in @gr-exports/head Package

@gr-exports/head Updated 02 Dec 2025

Summary

01/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191562: Malicious code in @gr-exports/head (npm). Affects @gr-exports/head versions 1.0.0 – 99.0.0. 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 @gr-exports/head package is a JavaScript library commonly used in Node.js applications to manage and manipulate the document head, including meta tags, title, and links. It is designed to enhance the SEO and usability of web applications. However, it has been identified as containing malicious code, which poses a significant risk to users and their applications.

Vulnerability Detail

The vulnerability in the @gr-exports/head package stems from the inclusion of malicious code that can compromise the integrity of applications utilizing this package. This malicious code can lead to unauthorized access, data breaches, or the execution of harmful scripts within the user's environment. The affected versions are 1.0.0 and 99.0.0, which have been flagged for their potential to introduce security risks.

How To Fix

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

npm uninstall @gr-exports/head

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

If immediate updating is not feasible, consider removing the @gr-exports/head package from your project until a secure version is released. This can be done using the command: npm uninstall @gr-exports/head. Additionally, monitor your application for any suspicious behavior that may arise from using the affected package.

Conclusion

The @gr-exports/head package has been identified as containing malicious code, posing a significant risk to applications that utilize it. Users are advised to update to a secure version or remove the package until a fix is available. Utilizing tools like Vulert can help monitor and manage vulnerabilities effectively.

See every vulnerability recorded for @gr-exports/head →

Share this vulnerability

FAQ

The @gr-exports/head package is a library for managing the document head in Node.js applications, allowing developers to manipulate meta tags and other head elements.

The affected versions are 1.0.0 and 99.0.0, which contain malicious code that can compromise application security.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in real-time. By analyzing your package-lock.json file, Vulert can help identify if your application is affected.

Yes, you can temporarily uninstall the @gr-exports/head package or replace it with an alternative package until a secure version is available.

Detailed information can be found on the GitHub repository of the malicious packages, as well as through security advisories related to npm packages.

How To Fix

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

npm uninstall @gr-exports/head

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