Critical Malicious Code Vulnerability in aztogh Package

aztogh Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15261: Malicious code in aztogh (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 aztogh package is an npm library designed for specific functionalities within JavaScript applications. It is utilized by developers for various tasks, but its recent discovery of malicious code poses significant risks. This vulnerability can lead to unauthorized access and potential exploitation of applications using this package.

Vulnerability Detail

The vulnerability identified in the aztogh package stems from the inclusion of malicious code that can compromise the security of applications utilizing it. This issue was introduced in version 0 and affects all subsequent versions. The ramifications of this vulnerability include unauthorized data access, potential data breaches, and exploitation of user systems. It is crucial for developers to be aware of this risk and take immediate action to mitigate it.

How To Fix

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

npm uninstall aztogh

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 avoid using the aztogh package in your application until a secure version is released. If you need similar functionality, consider using alternative packages that are verified and do not have known vulnerabilities.

Conclusion

The discovery of malicious code in the aztogh package poses a significant threat to applications using it. Developers must take immediate action to remove the package and monitor for updates. Utilizing tools like Vulert can help in identifying vulnerabilities in real-time.

See every vulnerability recorded for aztogh →

Share this vulnerability

FAQ

The aztogh package is an npm library used in JavaScript applications for various functionalities.

The malicious code can lead to unauthorized access and exploitation of applications that utilize the package.

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.

Currently, there is no patched version available. It is recommended to remove the package until a secure version is released.

You should remove the aztogh package from your project and look for alternative packages until a secure version is available.

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 aztogh

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