Malicious Code Vulnerability in audonizr: A Critical Security Risk

audonizr Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15037: Malicious code in audonizr (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The package audonizr is an npm library designed for enhancing web applications with various features. It is utilized by developers to streamline user interactions and improve functionality. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that depend on it.

Vulnerability Detail

The vulnerability in audonizr originates from the inclusion of malicious code within the package. This code can potentially compromise the security of applications using audonizr, leading to unauthorized access, data breaches, or other malicious activities. The presence of such code can severely impact the integrity and trustworthiness of the software relying on this package.

How To Fix

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

npm uninstall audonizr

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, consider replacing audonizr with an alternative package that provides similar functionality without the associated risks. Review your application’s dependencies and ensure that no other packages are indirectly relying on audonizr.

Conclusion

The discovery of malicious code in the audonizr package highlights the importance of regularly reviewing and updating dependencies in software projects. By taking proactive measures to address this vulnerability, developers can safeguard their applications and maintain user trust.

See every vulnerability recorded for audonizr →

Share this vulnerability

FAQ

The malicious code is designed to exploit vulnerabilities in applications, potentially leading to 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 your application without any signup.

If an immediate update is not possible, consider implementing a workaround by using an alternative package that offers similar features.

Yes, tools like Vulert can help monitor your package-lock.json file for vulnerabilities in real-time.

Failing to address this vulnerability could lead to severe security breaches, data loss, and damage to your application's reputation.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall audonizr

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