Critical Malicious Code Vulnerability in @kong/spec-renderer Package

@kong/spec-renderer Updated 25 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191455: Malicious code in @kong/spec-renderer (npm). Affects @kong/spec-renderer versions 1.101.10-pr.747.ed2920a.0. 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 @kong/spec-renderer package is a tool used in the Node.js ecosystem for rendering API specifications. It is designed to facilitate the development and documentation of APIs, providing developers with a structured way to define and visualize API endpoints. However, this package has been compromised, leading to significant security concerns.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the @kong/spec-renderer package, specifically in version 1.101.10-pr.747.ed2920a.0. This malicious code can fully compromise any computer running the package, allowing unauthorized access to sensitive information such as secrets and keys. The origin of this vulnerability is linked to the package being flagged by the GitHub Security Advisory (GHSA-3r2q-8jxp-mjmh) as containing embedded malicious code, which poses a severe risk to users and their systems.

How To Fix

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

npm uninstall @kong/spec-renderer

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 workaround, users should uninstall the @kong/spec-renderer package using the command: npm uninstall @kong/spec-renderer. Additionally, ensure that all sensitive information is secured and rotated to prevent unauthorized access.

Conclusion

The @kong/spec-renderer package has been identified as containing malicious code that poses a significant security risk. Users are urged to uninstall the package immediately and take necessary precautions to secure their systems. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for @kong/spec-renderer →

Share this vulnerability

FAQ

The malicious code can lead to full system compromise, allowing attackers to access sensitive information stored on the affected computer.

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

Immediately uninstall the package and rotate any secrets or keys stored on the affected system.

Currently, there is no patched version available for the compromised package. Users are advised to remove it entirely.

Vulert monitors and alerts users in real-time for open-source vulnerabilities using just the package-lock.json file, ensuring that your applications remain secure.

How To Fix

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

npm uninstall @kong/spec-renderer

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