Malicious Code Detected in @azet/api: A Critical Vulnerability Overview
Summary
MAL-2025-6685: Malicious code in @azet/api (npm). Affects @azet/api versions >= 1.0.0. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The @azet/api package is an npm library designed for interfacing with Azet's API services. It provides developers with tools to access various functionalities offered by Azet. However, this package has been flagged for containing malicious code, which poses significant security risks to applications that utilize it. The vulnerability stems from its communication with a domain associated with malicious activities, potentially leading to unauthorized command execution.
Vulnerability Detail
The vulnerability identified in the @azet/api package originates from version 1.0.0, where the package is known to execute commands linked to malicious behavior. This could allow attackers to manipulate the application, leading to data breaches, unauthorized access, or other harmful consequences. The malicious nature of the package is confirmed by the OpenSSF Package Analysis project, which has documented its association with harmful activities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @azet/apiIf 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 remove the @azet/api package from your project until a secure version is available. Use the following command to uninstall the package: npm uninstall @azet/api. This will prevent any malicious code from executing in your application.
Conclusion
The @azet/api package has been identified as malicious due to its execution of harmful commands. It is crucial for developers using this package to take immediate action by updating to a secure version or removing it from their projects. Utilizing tools like Vulert can help in monitoring and managing open-source vulnerabilities effectively.
See every vulnerability recorded for @azet/api →
FAQ
The vulnerability involves the package executing commands associated with malicious behavior, which can compromise application security.
You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.
If an immediate update is not possible, consider removing the package from your project as a temporary workaround to mitigate risks.
Yes, Vulert provides real-time monitoring for open-source vulnerabilities using just your package-lock.json file, ensuring you stay informed about potential threats.
Using the vulnerable @azet/api package can lead to unauthorized access, data breaches, and other security incidents that could harm your application and its users.
