Malicious Code Detected in google-chart Package - Security Alert

google-chart Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21704: Malicious code in google-chart (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The google-chart package is a popular npm library used for creating interactive charts and visualizations in web applications. It provides a simple interface for developers to integrate various types of charts into their projects. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the google-chart package. This code can potentially compromise the security of applications using the package, leading to unauthorized access, data breaches, or other malicious activities. The issue was identified by Amazon Inspector, highlighting the importance of scrutinizing third-party packages for security flaws.

How To Fix

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

npm uninstall google-chart

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 google-chart package from your project until a secure version is released. You can uninstall it using the following command: npm uninstall google-chart. Alternatively, look for other charting libraries that do not have known vulnerabilities.

Conclusion

The discovery of malicious code in the google-chart package poses a serious threat to applications that rely on it. It is crucial for developers to stay informed about vulnerabilities in their dependencies and take necessary actions to secure their applications. Regularly updating packages and utilizing tools like Vulert can help mitigate these risks.

See every vulnerability recorded for google-chart →

Share this vulnerability

FAQ

The google-chart package is used for creating interactive charts and visualizations in web applications, allowing developers to easily integrate various types of charts.

The specific details of the malicious code have not been disclosed, but it poses significant security risks, including potential unauthorized access and data breaches.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By analyzing your package-lock.json file, Vulert can help you determine if your application is affected.

Yes, Vulert provides real-time monitoring for open-source vulnerabilities without requiring access to your code or installation. You can check your application's status using the Vulert playground.

If an immediate update is not possible, consider removing the package or switching to an alternative charting library 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 google-chart

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