Malicious Code Detected in gestalt-accessibility-token Package

gestalt-accessibility-token Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21358: Malicious code in gestalt-accessibility-token (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 gestalt-accessibility-token package is an npm library designed to enhance accessibility features in web applications. It provides developers with tools to ensure that their applications are usable by individuals with disabilities. However, this package has been found to contain malicious code, posing a significant risk to users who integrate it into their projects.

Vulnerability Detail

The vulnerability in the gestalt-accessibility-token package originates from the inclusion of malicious code that can compromise the security of applications using this library. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected applications. The issue affects all versions of the package starting from its introduction, making it critical for users to address this vulnerability promptly.

How To Fix

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

npm uninstall gestalt-accessibility-token

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 measure, users can remove the gestalt-accessibility-token package from their project until a secure version is released. This can be done using the command: npm uninstall gestalt-accessibility-token.

Conclusion

The discovery of malicious code in the gestalt-accessibility-token package poses a serious threat to developers and users alike. It is essential to take immediate action by updating or removing the package to safeguard applications from potential attacks. Regular monitoring for vulnerabilities using tools like Vulert can help maintain the security of your projects.

See every vulnerability recorded for gestalt-accessibility-token →

Share this vulnerability

FAQ

It is an npm library that provides tools for enhancing accessibility in web applications.

The malicious code can lead to unauthorized access and potential data breaches in applications using the package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

Users are encouraged to check for updates to the gestalt-accessibility-token package and apply them as soon as they are available.

As a workaround, consider uninstalling the package until a secure version is released.

How To Fix

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

npm uninstall gestalt-accessibility-token

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