Malicious Code Detected in @kyriba/data-frontend Package - Version 1.0.2

@kyriba/data-frontend Updated 08 Jan 2026

Summary

08/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-164: Malicious code in @kyriba/data-frontend (npm). Affects @kyriba/data-frontend versions 1.0.2 – 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 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 @kyriba/data-frontend package is an npm library designed for data management in frontend applications. It provides various functionalities to streamline data handling and improve user experience. However, version 1.0.2 of this package has been identified as malicious, posing significant risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the @kyriba/data-frontend package arises from its malicious behavior, which includes communication with a domain linked to harmful activities and executing commands that can compromise system integrity. This behavior can lead to unauthorized access, data breaches, and potential exploitation of the affected systems.

How To Fix

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

npm uninstall @kyriba/data-frontend

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

If you cannot update the package immediately, consider removing the @kyriba/data-frontend package from your project until a safe version is available. You can do this by executing: npm uninstall @kyriba/data-frontend.

Conclusion

The @kyriba/data-frontend package version 1.0.2 has been identified as malicious, posing significant risks to applications. It is crucial to update to a patched version to mitigate these risks. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for @kyriba/data-frontend →

Share this vulnerability

FAQ

The package communicates with a domain associated with malicious activities and executes harmful commands.

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

As a temporary measure, you can uninstall the @kyriba/data-frontend package from your project.

Using the affected version can lead to unauthorized access, data breaches, and exploitation of your application.

Yes, Vulert provides a way to monitor vulnerabilities using just your package-lock.json file, ensuring you are alerted to any issues in real-time.

How To Fix

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

npm uninstall @kyriba/data-frontend

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