Critical Malicious Code Vulnerability in fixico Package

fixico Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20627: Malicious code in fixico (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The fixico package is an npm library designed for specific functionalities within JavaScript applications. It is utilized for various purposes, including data manipulation and API interactions. However, the package has been identified as containing malicious code, which poses significant security risks to applications that depend on it.

Vulnerability Detail

The vulnerability in the fixico package originates from the inclusion of malicious code that can compromise the integrity and security of applications using this package. This malicious code can lead to unauthorized access, data breaches, or other harmful actions within the application environment. The vulnerability affects all versions starting from 0, making it critical for users to take immediate action.

How To Fix

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

npm uninstall fixico

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, consider removing the fixico package from your project until a secure version is released. You can do this by running: npm uninstall fixico. This will prevent any potential exploitation of the malicious code while you await a fix.

Conclusion

The fixico package has been identified as containing malicious code, posing serious security risks to applications that utilize it. Users are urged to update or remove the package immediately to safeguard their applications. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for fixico →

Share this vulnerability

FAQ

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

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in real-time. Check your application against the vulnerability using the Vulert playground at Vulert Scanner.

If you are using fixico, you should immediately update to the latest patched version or remove the package from your project until a secure version is released.

Using a package with malicious code can lead to unauthorized access, data breaches, and potential damage to your application and its users.

Yes, you can use Vulert to monitor your project for vulnerabilities without needing to access the code or installation. It uses package-lock.json to provide real-time alerts.

How To Fix

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

npm uninstall fixico

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