Critical Malicious Code Vulnerability in 5xzkuy Package

5xzkuy Updated 19 Oct 2026

Summary

19/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17950: Malicious code in 5xzkuy (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The 5xzkuy package is an npm module that may be used for various functionalities within JavaScript applications. However, it has been identified as containing malicious code that compromises the security of any system where it is installed. This vulnerability poses a significant risk to developers and organizations relying on this package for their projects.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the 5xzkuy package. 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 can lead to data breaches and loss of control over the affected systems. Users are advised to treat any system with this package as compromised.

How To Fix

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

npm uninstall 5xzkuy

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 are no effective workarounds for this vulnerability other than removing the package and securing your system. Users should ensure that their systems are scanned for any residual malicious software that may have been installed alongside the package.

Conclusion

The discovery of malicious code within the 5xzkuy package poses a significant threat to users and their systems. Immediate action is required to mitigate the risks associated with this vulnerability. By uninstalling the package and securing sensitive information, users can protect themselves from potential breaches.

See every vulnerability recorded for 5xzkuy →

Share this vulnerability

FAQ

Immediately uninstall the package using npm uninstall 5xzkuy and rotate any sensitive information stored on the affected system.

You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.

Leaving the package installed can lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.

Regularly monitor your dependencies using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.

While many npm packages are safe, it is crucial to vet packages before installation and use tools like Vulert to monitor for vulnerabilities.

How To Fix

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

npm uninstall 5xzkuy

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