Malicious code in ui-header (npm)

ui-header Updated 02 Oct 2025

Summary

01/12/2023
CRITICAL
No i
Critical
Not published

MAL-2023-8650: Malicious code in ui-header (npm). Affects ui-header 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 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 'ui-header' package is an npm package that provides a UI header component for web applications. It is commonly used to create a consistent header across different pages of a web application. The package is widely used in various projects and has a version 1.0.0 that is affected by a malicious code vulnerability.

Vulnerability Detail

The 'ui-header' package version 1.0.0 has been identified as malicious by the OpenSSF Package Analysis project. The package communicates with a domain associated with malicious activity. This vulnerability can have severe consequences for applications that use this package, as it can lead to unauthorized access, data breaches, or other malicious actions. It is crucial to address this vulnerability promptly to ensure the security of the application.

How To Fix

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

npm uninstall ui-header

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

There is no known workaround for this vulnerability. It is essential to update the package to a non-malicious version as soon as possible.

Conclusion

The 'ui-header' package version 1.0.0 has been identified as malicious, posing a significant security risk to applications that use it. It is crucial to update the package to a non-malicious version as soon as possible to mitigate the vulnerability. For further support and guidance on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for ui-header →

Share this vulnerability

FAQ

You can use the Vulert Playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Simply provide your package-lock.json file, and Vulert will analyze it in real-time to identify any open-source vulnerabilities, including this malicious code in 'ui-header'.

This vulnerability can lead to unauthorized access, data breaches, or other malicious actions in applications that use the affected 'ui-header' package. Attackers may exploit the malicious code to gain control over the application, steal sensitive data, or perform unauthorized actions.

Yes, the recommended fix is to update the 'ui-header' package to a non-malicious version. The maintainers of the package should release a patched version that removes the malicious code. Developers should update their application's dependencies to the latest non-malicious version of 'ui-header' to mitigate the vulnerability.

No, there are no known workarounds for this vulnerability. It is crucial to update the package to a non-malicious version as soon as possible.

For further support on vulnerability remediation, you can contact info@devnack.com. They can provide guidance and assistance in addressing this vulnerability and ensuring the security of your application.

How To Fix

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

npm uninstall ui-header

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