Critical Malicious Code Vulnerability in @indigo-multi/fonts Package

@indigo-multi/fonts Updated 02 Oct 2025

Summary

15/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-5878: Malicious code in @indigo-multi/fonts (npm). Affects @indigo-multi/fonts versions 1.0.0 – 5.0.2. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The @indigo-multi/fonts package is an npm library designed to provide various font styles for web applications. It is commonly used by developers to enhance the visual appeal of their projects. However, this package has been identified to contain malicious code that compromises the security of any system it is installed on, making it a significant risk for users.

Vulnerability Detail

The vulnerability originates from the inclusion of embedded malicious code within the @indigo-multi/fonts package. This code can lead to full compromise of any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code poses severe risks, as it may not only affect the immediate environment but can also propagate further vulnerabilities within the system.

How To Fix

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

npm uninstall @indigo-multi/fonts

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

There are no effective workarounds for this vulnerability other than removing the package entirely. Ensure to monitor your system for any unusual activity after removal.

Conclusion

The @indigo-multi/fonts package has been identified as containing malicious code that poses a significant security risk. Immediate action is required to remove the package and secure any sensitive information. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for @indigo-multi/fonts →

Share this vulnerability

FAQ

You should immediately remove the package and rotate any sensitive information stored on your system.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

Failing to remove the package can lead to unauthorized access to your system, potentially compromising sensitive data and allowing further malicious activities.

Regularly monitor your dependencies using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.

It is advisable to review other packages from the same author and check for any reported vulnerabilities before using them.

How To Fix

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

npm uninstall @indigo-multi/fonts

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