Critical Malicious Code Vulnerability in agifbaig Package

agifbaig Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14158: Malicious code in agifbaig (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 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 agifbaig package is an npm library that serves a specific functionality within JavaScript applications. It is designed to facilitate certain tasks, but it has been identified as containing malicious code that poses a significant security risk to users and their applications. This vulnerability can lead to unauthorized access or data breaches, making it essential for developers to address it promptly.

Vulnerability Detail

The vulnerability in the agifbaig package arises from the inclusion of malicious code that can execute harmful actions within the user's environment. This code was introduced in version 0 and can compromise the integrity of applications that depend on this package. The ramifications of this vulnerability include potential data theft, unauthorized access to sensitive information, and disruption of application functionality. It is crucial for developers to recognize the risks associated with using this package and take immediate action to mitigate them.

How To Fix

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

npm uninstall agifbaig

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 agifbaig package in your application until a secure version is released. Monitor your application for any signs of compromise and ensure that you have proper security measures in place.

Conclusion

The agifbaig package has been identified as containing malicious code that poses a serious threat to applications using it. Developers are urged to uninstall the package and seek alternatives to ensure the security of their applications. Regular monitoring for vulnerabilities is essential to maintain application integrity.

See every vulnerability recorded for agifbaig →

Share this vulnerability

FAQ

The agifbaig package is an npm library used in JavaScript applications for specific functionalities, but it has been found to contain malicious code.

The malicious code can lead to unauthorized access, data breaches, and disruption of application functionality, posing significant security risks.

You should uninstall the agifbaig package immediately and replace it with a secure alternative to protect your application.

No, there is currently no patch available for the agifbaig package. The best course of action is to remove it from your project.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json. You can check your application for vulnerabilities without signing up at the Vulert playground.

How To Fix

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

npm uninstall agifbaig

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