Malicious code in cobrowse-visitor (npm)

cobrowse-visitor Updated 02 Oct 2025

Summary

20/11/2023
CRITICAL
No i
Critical
Not published

MAL-2023-8542: Malicious code in cobrowse-visitor (npm). Affects cobrowse-visitor versions 9.9.9. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The cobrowse-visitor package is an npm package used for cobrowsing functionality. It allows users to share their screens with others for collaborative browsing. The package is widely used in various applications and provides a convenient way for users to interact and collaborate online. However, a recent vulnerability has been discovered in the package, which exposes users to potential malicious code execution.

Vulnerability Detail

The vulnerability in cobrowse-visitor (npm) is a result of the presence of malicious code in the package. This code can compromise the security of any computer that has the package installed or running. It is advised to consider any computer with this package as fully compromised. All secrets and keys stored on the affected computer should be rotated immediately from a different computer. While removing the package is recommended, it may not guarantee the removal of all malicious software installed as a result of its installation.

How To Fix

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

npm uninstall cobrowse-visitor

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 is no specific workaround mentioned for this vulnerability. It is recommended to follow the steps mentioned in the 'how_to_fix' section to mitigate the issue.

Conclusion

The cobrowse-visitor package has been found to contain malicious code, compromising the security of computers where it is installed. It is important to take immediate action by rotating secrets and keys, removing the package, and conducting a security audit. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for cobrowse-visitor →

Share this vulnerability

FAQ

Cobrowse-visitor is an npm package used for cobrowsing functionality, allowing users to share their screens with others for collaborative browsing.

The vulnerability in cobrowse-visitor exposes users to potential malicious code execution, compromising the security of their computers.

If you have cobrowse-visitor installed, it is recommended to consider your computer as fully compromised. Rotate all secrets and keys stored on the affected computer from a different computer and remove the package.

While removing the cobrowse-visitor package is advised, there is no guarantee that it will remove all malicious software resulting from its installation. A thorough security audit is recommended.

After removing the cobrowse-visitor package, it is crucial to perform a thorough security audit to ensure the removal of any remaining malicious software.

How To Fix

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

npm uninstall cobrowse-visitor

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