Critical Malicious Code Vulnerability in fig-kilo-dloy Package

fig-kilo-dloy Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20479: Malicious code in fig-kilo-dloy (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 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 fig-kilo-dloy package is an npm module designed for specific functionalities within JavaScript applications. It is utilized by developers for various tasks, but its recent discovery of malicious code poses a significant threat to users. This vulnerability can compromise the integrity of applications relying on this package, making it crucial for developers to be aware of its risks.

Vulnerability Detail

The vulnerability in the fig-kilo-dloy package originates from the inclusion of malicious code that can execute harmful actions within the user's environment. This malicious code can lead to unauthorized access, data breaches, or even system compromise. The issue was introduced in version 0 of the package and remains unaddressed, making it imperative for users to take immediate action to mitigate potential risks.

How To Fix

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

npm uninstall fig-kilo-dloy

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, users can avoid using the fig-kilo-dloy package altogether and seek alternative packages that offer similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the fig-kilo-dloy package poses serious risks to users and their applications. Immediate action is required to remove the package and safeguard against potential threats. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for fig-kilo-dloy →

Share this vulnerability

FAQ

The fig-kilo-dloy package is an npm module used in JavaScript applications for various functionalities, but it has been found to contain malicious code.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.

If you have installed fig-kilo-dloy, it is recommended to remove it immediately and look for alternative packages.

Currently, there is no patched version available for the fig-kilo-dloy package, so removal is the best course of action.

Using the fig-kilo-dloy package can lead to unauthorized access, data breaches, and system compromise due to the malicious code it contains.

How To Fix

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

npm uninstall fig-kilo-dloy

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