Malicious Code Detected in aog-lib Package: Version 2.2.4 and 2.2.5 Compromised

aog-lib Updated 02 Oct 2025

Summary

16/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6889: Malicious code in aog-lib (npm). Affects aog-lib versions 2.2.4 – 2.2.5. 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 'aog-lib' package is a JavaScript library available on npm, designed to facilitate various functionalities in web applications. It is widely used for its ease of integration and utility in enhancing application features. However, recent analyses have revealed that specific versions of this package contain malicious code that compromises user security.

Vulnerability Detail

The vulnerability in the 'aog-lib' package arises from its communication with a domain linked to malicious activities. This behavior indicates that the package may execute commands that can lead to unauthorized access or data breaches. The identified malicious versions, 2.2.4 and 2.2.5, have been flagged by the OpenSSF Package Analysis project, highlighting the potential risks associated with using these versions in production environments.

How To Fix

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

npm uninstall aog-lib

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 measure, you can remove the 'aog-lib' package from your project until a secure version is confirmed. Use the following command to uninstall it: 'npm uninstall aog-lib'. This will prevent any malicious code from executing in your application.

Conclusion

The 'aog-lib' package has been identified as containing malicious code in specific versions, posing significant security risks. Users are advised to update to a secure version or remove the package until a fix is confirmed. Utilizing tools like Vulert can help maintain awareness of vulnerabilities in your software.

See every vulnerability recorded for aog-lib →

Share this vulnerability

FAQ

Versions 2.2.4 and 2.2.5 of the 'aog-lib' package are identified as malicious.

You can use Vulert, which monitors open-source vulnerabilities in your software. By analyzing your package-lock.json file, Vulert can alert you in real-time. You can also check your application using the Vulert playground at Vulert Scanner without any signup.

If immediate updates are not feasible, consider removing the package temporarily to mitigate risks until a secure version is available.

Using the affected versions may lead to unauthorized access, data breaches, or other malicious activities that could compromise your application's integrity.

Yes, tools like Vulert can help you monitor your dependencies for vulnerabilities in real-time, ensuring that you are alerted to any issues as they arise.

How To Fix

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

npm uninstall aog-lib

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