Critical Malicious Code Vulnerability in asepxyznew Package

asepxyznew Updated 09 Oct 2026

Summary

09/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17737: Malicious code in asepxyznew (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The asepxyznew package is an npm library that is designed for specific functionalities within JavaScript applications. It is commonly used by developers for its ease of integration and utility features. However, this package has been compromised, embedding malicious code that poses significant security risks to any system utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the asepxyznew package, which has been identified as a severe threat. Any system with this package installed is considered fully compromised, potentially allowing unauthorized access to sensitive information such as secrets and keys. The malicious code can lead to further exploitation, making it critical for users to take immediate action.

How To Fix

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

npm uninstall asepxyznew

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 workaround, ensure that all secrets and keys stored on the compromised system are rotated immediately from a different, secure computer. This step is crucial to mitigate any potential damage caused by the malicious code.

Conclusion

The asepxyznew package has been identified as containing malicious code, posing a severe risk to any system using it. Immediate removal of the package and rotation of sensitive information is essential to mitigate potential damage. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for asepxyznew →

Share this vulnerability

FAQ

The asepxyznew package is an npm library used in JavaScript applications for various functionalities, but it has been compromised with malicious code.

If you have the asepxyznew package installed, your system is considered compromised. You can use tools like Vulert to monitor and alert for vulnerabilities.

You should immediately remove the asepxyznew package and rotate any sensitive information stored on the affected system.

Currently, there is no patch available. The best course of action is to remove the package entirely.

Vulert monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file, providing real-time insights without requiring code access.

How To Fix

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

npm uninstall asepxyznew

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