Malicious Code Detected in aimaze: A Critical Vulnerability

aimaze Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14177: Malicious code in aimaze (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 'aimaze' package is an npm library designed for specific functionalities within JavaScript applications. It is utilized by developers for its ease of integration and utility in various projects. However, it has been identified to contain malicious code, posing significant security risks to applications that incorporate it.

Vulnerability Detail

The vulnerability in the 'aimaze' package stems from the inclusion of malicious code that can compromise the integrity and security of applications using this package. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue was introduced in version 0 and affects all subsequent versions.

How To Fix

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

npm uninstall aimaze

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 'aimaze' package altogether and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the 'aimaze' package highlights the importance of vigilant monitoring of open-source dependencies. Developers should take immediate action to remove the affected package and consider alternatives to safeguard their applications.

See every vulnerability recorded for aimaze →

Share this vulnerability

FAQ

The malicious code can potentially allow unauthorized access to sensitive data or system resources, leading to security breaches.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By simply uploading your package-lock.json file, you can check for vulnerabilities without needing to install any software.

The best mitigation strategy is to remove the 'aimaze' package from your project and replace it with a secure alternative.

You should immediately remove the 'aimaze' package from your application and deploy a version without it to prevent potential exploitation.

You can visit the Vulert website, which provides insights and alerts on open-source vulnerabilities, helping you stay informed about potential risks.

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 aimaze

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