Malicious Code Detected in astro-benchmark Package - Security Alert

astro-benchmark Updated 02 Oct 2025

Summary

30/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6696: Malicious code in astro-benchmark (npm). Affects astro-benchmark versions >= 1.4.5. 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 astro-benchmark package is a tool designed for benchmarking and performance testing in JavaScript applications. It provides developers with the ability to measure and analyze the performance of their code. However, recent findings have revealed that this package has been compromised, allowing it to communicate with a domain linked to malicious activities, posing a significant risk to users and their applications.

Vulnerability Detail

The vulnerability in the astro-benchmark package arises from its ability to connect to a malicious domain, which can lead to unauthorized data access, potential data breaches, and exploitation of the user's environment. This issue was introduced in version 1.4.5, making it critical for users to be aware of the risks associated with using this version or any subsequent versions that have not been patched.

How To Fix

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

npm uninstall astro-benchmark

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 astro-benchmark package until a secure version is released. Alternatively, consider using other benchmarking tools that do not have known vulnerabilities.

Conclusion

The astro-benchmark package has been found to contain malicious code that poses a security threat to users. It is crucial to update the package to a secure version as soon as possible and to monitor your applications for any vulnerabilities using tools like Vulert.

See every vulnerability recorded for astro-benchmark →

Share this vulnerability

FAQ

Astro-benchmark is a JavaScript package used for performance benchmarking and testing in applications.

The vulnerability allows the package to communicate with a malicious domain, which can lead to security risks such as data breaches.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

If you cannot update the package right away, consider using alternative benchmarking tools or refrain from using the astro-benchmark package until a fix is available.

The vulnerability was identified by Amazon Inspector, a security tool that helps in identifying vulnerabilities in software packages.

How To Fix

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

npm uninstall astro-benchmark

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