Critical Malicious Code Vulnerability in transform-react-display-name Package

transform-react-display-name Updated 06 Feb 2026

Summary

03/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-666: Malicious code in transform-react-display-name (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 transform-react-display-name package is an npm library used primarily in React applications to enhance the debugging experience by providing meaningful names for components. It is widely utilized for its simplicity and effectiveness in improving the readability of React component hierarchies. However, recent findings have revealed that this package contains malicious code, posing significant security risks to any application that incorporates it.

Vulnerability Detail

The vulnerability stems from the discovery of embedded malicious code within the transform-react-display-name package. This code can compromise any system where the package is installed, leading to unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code has been confirmed by multiple sources, including Amazon Inspector and GHSA malware reports. Systems running this package should be considered fully compromised, and the implications of this vulnerability are severe, as it may allow external entities to gain full control over affected computers.

How To Fix

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

npm uninstall transform-react-display-name

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 workaround, you can temporarily disable any functionality that relies on the transform-react-display-name package until it is removed and replaced with a secure alternative. Ensure that you audit your project dependencies regularly to avoid similar vulnerabilities in the future.

Conclusion

The discovery of malicious code in the transform-react-display-name package highlights the importance of maintaining vigilance in software dependencies. Immediate action is required to mitigate risks associated with this vulnerability, including the removal of the package and the rotation of sensitive information. Utilizing tools like Vulert can aid in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for transform-react-display-name →

Share this vulnerability

FAQ

You should immediately remove the package and rotate any secrets or keys stored on the affected system.

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

As of now, there is no patched version available. It is recommended to remove the package entirely.

Failure to address this vulnerability can lead to unauthorized access to sensitive data and complete control of your system by malicious actors.

Yes, but you may need to find an alternative solution for the functionality provided by the transform-react-display-name package.

How To Fix

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

npm uninstall transform-react-display-name

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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.