Malicious Code Detected in biagio Package - Security Alert

biagio Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15658: Malicious code in biagio (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 biagio package is an npm library designed for specific functionalities within JavaScript applications. It is utilized by developers for various tasks, but its recent identification as containing malicious code raises significant security concerns. This vulnerability can potentially compromise applications that rely on this package, making it crucial for users to be aware of its implications.

Vulnerability Detail

The biagio package has been found to contain malicious code that can lead to unauthorized access or manipulation of user data. This vulnerability originated from the package's codebase, which was intentionally compromised. The ramifications include potential data breaches, loss of user trust, and the possibility of further exploitation by malicious actors. It is essential for developers using this package to understand the risks associated with its use.

How To Fix

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

npm uninstall biagio

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, developers can remove the biagio package from their project until a secure version is released. This can be done using the command: npm uninstall biagio. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the biagio package poses a significant threat to applications that utilize it. Developers must take immediate action to update or remove the package to safeguard their applications and users. Awareness and proactive measures are essential in maintaining software security.

See every vulnerability recorded for biagio →

Share this vulnerability

FAQ

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

Malicious code was detected in the biagio package, posing security risks to applications that utilize it.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.

Immediately update the biagio package to the latest patched version or uninstall it until a secure version is available.

Using the compromised biagio package can lead to unauthorized access to user data, data breaches, and loss of user trust.

How To Fix

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

npm uninstall biagio

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