Malicious Code Detected in @kyriba/mf-kit: Version 1.0.3 Compromised

@kyriba/mf-kit Updated 08 Jan 2026

Summary

08/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-165: Malicious code in @kyriba/mf-kit (npm). Affects @kyriba/mf-kit versions 1.0.3. 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 package @kyriba/mf-kit is a Node.js library available via npm, designed to facilitate various functionalities for developers. However, version 1.0.3 has been identified as malicious, posing significant risks to users who integrate it into their applications. The package's malicious behavior includes unauthorized communication with harmful domains and executing potentially dangerous commands.

Vulnerability Detail

The vulnerability in @kyriba/mf-kit arises from its malicious code, which communicates with domains linked to malicious activities. This behavior can lead to unauthorized access, data breaches, and execution of harmful commands within the user's environment. The origin of this vulnerability was identified by the OpenSSF Package Analysis project, which flagged the package due to its malicious actions.

How To Fix

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

npm uninstall @kyriba/mf-kit

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 measure, you can avoid using the affected package altogether. If your project relies on its functionality, consider looking for alternative packages that provide similar features without the associated risks.

Conclusion

The discovery of malicious code in @kyriba/mf-kit version 1.0.3 highlights the importance of vigilance when using open-source packages. Users must take immediate action to remove the affected version and consider alternatives to safeguard their applications from potential threats.

See every vulnerability recorded for @kyriba/mf-kit →

Share this vulnerability

FAQ

The vulnerability involves malicious code that communicates with harmful domains and executes unauthorized commands.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

You should uninstall version 1.0.3 immediately and update to a secure version of the package.

While specific exploits have not been detailed, the malicious behavior could lead to unauthorized access and data breaches.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert and keep your packages updated to their latest secure versions.

How To Fix

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

npm uninstall @kyriba/mf-kit

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