Critical Malicious Code Vulnerability in asdfgh3 Package

asdfgh3 Updated 11 Dec 2025

Summary

11/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192439: Malicious code in asdfgh3 (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 asdfgh3 package is a JavaScript library available through npm, commonly used for various functionalities in web development. It is designed to provide developers with tools to enhance their applications. However, this package has been identified to contain malicious code, posing significant risks to applications that utilize it.

Vulnerability Detail

The vulnerability originates from the discovery of malicious code within the asdfgh3 package, identified by Amazon Inspector. This malicious code can potentially compromise the security of applications that depend on this package, leading to unauthorized access, data breaches, or other malicious activities. The vulnerability affects all versions of the package starting from its introduction, 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 asdfgh3

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 avoid using the asdfgh3 package in your project until a secure version is released. If you must use it, consider isolating it in a controlled environment to minimize potential risks.

Conclusion

The discovery of malicious code in the asdfgh3 package presents a serious security threat to applications that utilize it. Immediate action is required to remove the package and monitor for updates. Utilizing tools like Vulert can help in identifying vulnerabilities in your applications effectively.

See every vulnerability recorded for asdfgh3 →

Share this vulnerability

FAQ

The asdfgh3 package is a JavaScript library available on npm, used for various functionalities in web development.

The specific nature of the malicious code has not been disclosed, but it poses significant risks such as unauthorized access and data breaches.

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

Immediately remove the asdfgh3 package from your project and monitor for any updates or patches that may address the vulnerability.

If you must use the package, consider isolating it in a controlled environment and avoid exposing sensitive data.

How To Fix

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

npm uninstall asdfgh3

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