Malicious Code Detected in gccwrap Package - Security Alert

gccwrap Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21230: Malicious code in gccwrap (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 gccwrap package is an npm library designed to facilitate the use of GCC (GNU Compiler Collection) in various development environments. It is commonly utilized for compiling C and C++ programs. However, this package has been found to contain malicious code, posing significant security risks to users who integrate it into their projects.

Vulnerability Detail

The vulnerability in the gccwrap package originates from the inclusion of malicious code that can compromise the security of applications using this library. This malicious code may lead to unauthorized access, data breaches, or system exploitation. Users of gccwrap are at risk of having their systems manipulated or sensitive information stolen due to this vulnerability.

How To Fix

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

npm uninstall gccwrap

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, users can avoid using the gccwrap package until a secure version is confirmed. Alternatively, consider using other trusted packages that provide similar functionality without the associated risks.

Conclusion

The gccwrap package has been found to contain malicious code, posing serious security threats to users. It is crucial to update to a secure version or consider alternative solutions to mitigate risks. Regular monitoring of dependencies using tools like Vulert can help maintain application security.

See every vulnerability recorded for gccwrap →

Share this vulnerability

FAQ

gccwrap is an npm package that helps developers use the GNU Compiler Collection for compiling C and C++ programs.

The malicious code was identified by security researchers from Amazon Inspector, who reported the findings to the community.

Using the compromised gccwrap package can lead to unauthorized access to your system, data breaches, and potential exploitation by attackers.

You can use Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

If immediate updates are not possible, consider using alternative packages that offer similar functionality and are known to be secure.

How To Fix

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

npm uninstall gccwrap

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