Critical Malicious Code Vulnerability in @ensdomains/ui Package

@ensdomains/ui Updated 24 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190813: Malicious code in @ensdomains/ui (npm). Affects @ensdomains/ui versions 3.4.6. 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 @ensdomains/ui package is a JavaScript library used in the npm ecosystem, primarily for building user interfaces related to Ethereum Name Service (ENS). It provides essential functionalities for developers to create applications that interact with ENS. However, this package has been compromised, leading to significant security concerns.

Vulnerability Detail

The vulnerability originates from malicious code embedded within the @ensdomains/ui package, specifically in version 3.4.6. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The implications of this vulnerability are severe, as it may lead to data breaches and unauthorized control over affected systems.

How To Fix

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

npm uninstall @ensdomains/ui

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, avoid using the @ensdomains/ui package until it has been confirmed safe. If you must use it, consider isolating the environment where it is installed to minimize potential damage.

Conclusion

The @ensdomains/ui package has been identified as containing malicious code that poses a significant security risk. Immediate action is required to remove the package and secure any affected systems. Stay informed about updates and patches for this package to ensure the safety of your applications.

See every vulnerability recorded for @ensdomains/ui →

Share this vulnerability

FAQ

Immediately remove the package and rotate any secrets or keys stored on the affected system.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.

Currently, there is no patched version available. It is recommended to remove the package until a safe version is released.

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

It is not recommended to use the package until it has been verified as safe. Consider alternative packages or solutions.

How To Fix

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

npm uninstall @ensdomains/ui

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