Critical Malicious Activity Detected in azuresdkpackagelist Package

azuresdkpackagelist Updated 02 Oct 2025

Summary

01/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6697: Malicious code in azuresdkpackagelist (npm). Affects azuresdkpackagelist versions >= 1.1.2. 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 azuresdkpackagelist package is an npm library that is used to manage and list Azure SDK packages. It is designed to facilitate the integration of Azure services into applications. However, this package has been identified as having a vulnerability that allows it to communicate with a domain associated with malicious activities, potentially compromising user data and application integrity.

Vulnerability Detail

The vulnerability arises from the package's ability to connect to a malicious domain, which can lead to unauthorized data access, data exfiltration, or other harmful actions. This issue was introduced in version 1.1.2 of the package, making it critical for users to be aware of the risks associated with using this version or any earlier versions. The malicious communication can be exploited by attackers to execute harmful scripts or steal sensitive information.

How To Fix

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

npm uninstall azuresdkpackagelist

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 workaround, you can remove the azuresdkpackagelist package from your project until a secure version is released. You can do this by executing: npm uninstall azuresdkpackagelist.

Conclusion

The azuresdkpackagelist package has a critical vulnerability that allows it to communicate with a malicious domain, posing significant risks to applications that utilize it. Users are strongly advised to update to a secure version or remove the package until a fix is available. Utilizing tools like Vulert can help in monitoring for such vulnerabilities effectively.

See every vulnerability recorded for azuresdkpackagelist →

Share this vulnerability

FAQ

The azuresdkpackagelist package is used to manage and list Azure SDK packages for easier integration into applications.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check if your application is affected by this vulnerability using the Vulert playground without any signup at Vulert Scanner.

If you cannot update the package right away, consider removing it from your project as a temporary measure to mitigate risks.

Using the vulnerable version can expose your application to data breaches, unauthorized access, and other malicious activities due to its communication with a harmful domain.

Yes, tools like Vulert can help you monitor your dependencies for vulnerabilities in real-time without needing access to your code or installation.

How To Fix

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

npm uninstall azuresdkpackagelist

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