Critical Malicious Code Vulnerability in xsjukcnv8low26 Package

xsjukcnv8low26 Updated 23 Sep 2026

Summary

23/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-16460: Malicious code in xsjukcnv8low26 (npm). Affects xsjukcnv8low26 versions 1.0.0 – 1.0.1. 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 xsjukcnv8low26 package is an npm library that is used in various JavaScript applications. It is designed to facilitate specific functionalities within these applications. However, this package has been identified to contain malicious code, posing significant security risks to any system that utilizes it. The presence of such vulnerabilities can lead to unauthorized access and compromise of sensitive information.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the xsjukcnv8low26 package. This code can potentially allow an attacker to gain full control over any system where the package is installed. The malicious nature of the code means that any secrets or keys stored on the affected system should be considered compromised. The source of this vulnerability has been traced back to both Amazon Inspector and GHSA malware reports, indicating a serious threat to users of this package.

How To Fix

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

npm uninstall xsjukcnv8low26

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, you can prevent the execution of the malicious code by uninstalling the package using the command: npm uninstall xsjukcnv8low26. However, be aware that this may not eliminate all traces of the malicious software.

Conclusion

The xsjukcnv8low26 package has been identified as containing malicious code, posing a significant security risk. Immediate action is required to uninstall the package and secure any compromised secrets. Users are encouraged to utilize tools like Vulert for ongoing monitoring of vulnerabilities in their projects.

See every vulnerability recorded for xsjukcnv8low26 →

Share this vulnerability

FAQ

You should immediately uninstall the package and rotate any secrets or keys stored on your system.

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

Currently, there is no patched version available. It is recommended to uninstall the package until further notice.

Failure to address this vulnerability may lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.

Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities using just your package-lock.json file.

How To Fix

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

npm uninstall xsjukcnv8low26

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