Malicious Code Detected in comlabs Package - Security Alert

comlabs Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17399: Malicious code in comlabs (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 comlabs package is a Node.js library commonly used in various applications for its functionalities related to communication and collaboration tools. It is designed to facilitate seamless interactions within software environments. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the comlabs package arises from the inclusion of malicious code that can compromise the security of applications using it. This code may allow unauthorized access, data breaches, or other harmful activities within the affected systems. The malicious nature of this code was identified by Amazon Inspector, highlighting the urgent need for users to address this issue promptly.

How To Fix

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

npm uninstall comlabs

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 workaround, users may consider removing the comlabs package from their project until a secure version is available. This can be done using the command: 'npm uninstall comlabs'. Additionally, consider using alternative packages that provide similar functionalities without the associated risks.

Conclusion

The discovery of malicious code in the comlabs package poses a significant threat to applications utilizing it. Immediate action is required to update or remove the package to safeguard against potential security breaches. Users are encouraged to leverage tools like Vulert for ongoing monitoring of vulnerabilities in their software.

See every vulnerability recorded for comlabs →

Share this vulnerability

FAQ

The malicious code can potentially allow unauthorized access and data breaches, posing serious security threats to applications.

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

Yes, users are advised to update to the latest patched version of the comlabs package to mitigate the vulnerability.

As a temporary measure, consider uninstalling the comlabs package and using alternative solutions until a secure version is available.

The malicious code was identified by Amazon Inspector, a security tool that helps in detecting vulnerabilities in software packages.

How To Fix

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

npm uninstall comlabs

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