Malicious Code Detected in Conversa Package (npm)

conversa Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17522: Malicious code in conversa (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 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 Conversa package is a JavaScript library used within the npm ecosystem, designed to facilitate communication features in applications. It is widely utilized for its ease of integration and functionality. However, recent findings have revealed that this package contains malicious code, posing significant risks to users and their applications.

Vulnerability Detail

The vulnerability in the Conversa package stems from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code may allow unauthorized access, data exfiltration, or other harmful actions, potentially leading to severe consequences for developers and end-users alike. The malicious code was introduced in version 0 and affects all subsequent versions.

How To Fix

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

npm uninstall conversa

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, you can remove the Conversa package from your project until a secure version is released. Use the following command to uninstall the package: 'npm uninstall conversa'. This will prevent any potential exploitation of the malicious code while you await a fix.

Conclusion

The discovery of malicious code in the Conversa package highlights the importance of vigilance in managing open-source dependencies. Users are encouraged to update or remove the package to protect their applications from potential threats. Utilizing tools like Vulert can further enhance security by providing real-time alerts for vulnerabilities.

See every vulnerability recorded for conversa →

Share this vulnerability

FAQ

The malicious code can lead to unauthorized access and data breaches, compromising the integrity of applications using the package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

Currently, there is no specific patched version mentioned. It is advisable to monitor the package repository for updates.

If an immediate update is not possible, consider removing the package as a temporary measure to mitigate risks.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert and keep your packages updated to the latest secure versions.

How To Fix

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

npm uninstall conversa

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