Malicious Code Detected in uipagain Package - npm Vulnerability

uipagain Updated 23 Mar 2026

Summary

23/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-2085: Malicious code in uipagain (npm). Affects uipagain versions 1.0.0. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The 'uipagain' package, version 1.0.0, is a Node.js library available through npm. It is designed to facilitate user interface interactions in web applications. However, this package has been flagged for malicious activity, specifically for communicating with a domain linked to harmful actions. This raises significant security concerns for developers and users relying on this package for their applications.

Vulnerability Detail

The vulnerability in the 'uipagain' package arises from its ability to communicate with a domain associated with malicious activities. This could lead to unauthorized data access, data breaches, or the execution of harmful code within applications that utilize this package. The OpenSSF Package Analysis project identified this issue, emphasizing the need for immediate attention to prevent potential exploitation.

How To Fix

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

npm uninstall uipagain

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, you can avoid using the 'uipagain' package and look for alternative libraries that offer similar features without the associated risks. Always validate the security of any third-party packages before integrating them into your projects.

Conclusion

The 'uipagain' package has been identified as malicious due to its communication with a harmful domain. Developers should take immediate action to remove this package from their projects and seek alternative solutions to ensure the security of their applications.

See every vulnerability recorded for uipagain →

Share this vulnerability

FAQ

The 'uipagain' package is a Node.js library used for user interface interactions in web applications.

'uipagain' is considered malicious because it communicates with a domain linked to harmful activities, posing security risks.

You can use Vulert, which monitors and alerts for open-source vulnerabilities. Visit the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

If you have used 'uipagain', it is crucial to uninstall the package immediately and look for secure alternatives.

No patches are available for 'uipagain' as it has been flagged as malicious. The best course of action is to remove it from your project.

How To Fix

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

npm uninstall uipagain

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