Critical Malicious Code Vulnerability in secguest-lib Package

secguest-lib Updated 09 Jan 2026

Summary

09/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-169: Malicious code in secguest-lib (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 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 secguest-lib package is an npm library designed for various functionalities within JavaScript applications. However, it has been identified as containing malicious code that compromises the security of any system where it is installed. This vulnerability poses a significant risk to developers and organizations relying on this package for their projects.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the secguest-lib package. Any system running this package is considered fully compromised, with potential unauthorized access to sensitive information, including secrets and keys. The malicious code can lead to severe ramifications, including 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 secguest-lib

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, it is advised to uninstall the secguest-lib package using the following command: npm uninstall secguest-lib. Additionally, ensure that you review your system for any other potential malicious software that may have been installed as a result of this vulnerability.

Conclusion

The secguest-lib package poses a critical security risk due to embedded malicious code. Immediate removal of the package and rotation of sensitive information is necessary to mitigate potential damage. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for secguest-lib →

Share this vulnerability

FAQ

secguest-lib is an npm package used in JavaScript applications, but it has been found to contain malicious code.

If you have the secguest-lib package installed, your system is considered compromised. It is essential to take immediate action.

You should rotate all secrets and keys immediately from a different, secure computer to prevent unauthorized access.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without any signup.

How To Fix

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

npm uninstall secguest-lib

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