Critical Malicious Code Vulnerability in @trigo/keycloak-api Package

@trigo/keycloak-api Updated 24 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190687: Malicious code in @trigo/keycloak-api (npm). Affects @trigo/keycloak-api versions 1.3.1. 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 @trigo/keycloak-api package is a Node.js library designed to facilitate interactions with Keycloak, an open-source identity and access management solution. This package allows developers to integrate authentication and authorization features into their applications seamlessly. However, it has been identified to contain malicious code, posing significant security risks to any system where it is installed.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within version 1.3.1 of the @trigo/keycloak-api package. This code can compromise the entire system, allowing unauthorized access to sensitive information such as secrets and keys. The origin of this vulnerability is linked to a malicious actor who has manipulated the package, making any computer running it fully compromised. The ramifications include potential data breaches and loss of control over the affected systems.

How To Fix

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

npm uninstall @trigo/keycloak-api

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

Currently, there are no effective workarounds to mitigate the risks posed by this malicious code. The best course of action is to uninstall the package and secure the system.

Conclusion

The @trigo/keycloak-api package has been identified as containing malicious code that poses a severe security risk. Immediate action is required to remove the package and secure any affected systems. Users are encouraged to utilize tools like Vulert for ongoing monitoring of vulnerabilities in their applications.

See every vulnerability recorded for @trigo/keycloak-api →

Share this vulnerability

FAQ

The malicious code can lead to full system compromise, allowing unauthorized access to sensitive data.

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

Immediately remove the @trigo/keycloak-api package and rotate any secrets or keys stored on the affected system.

As of now, there is no patched version available. The package should be removed entirely.

Vulert monitors and alerts in real-time for open-source vulnerabilities using just the package-lock.json file, without requiring code access or installation.

How To Fix

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

npm uninstall @trigo/keycloak-api

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