Malware in conversa-sdk
Malware was discovered in the conversa-sdk npm package. Systems with the package installed or running should be considered fully compromised, requiring immediate rotation of all secrets and keys from a different computer.
- Disclosed
- Last updated
- Blast radius
- Any system with conversa-sdk installed or running
- Ecosystems
- Attack vectors
- Affected entities
- conversa-sdknpm package
The conversa-sdk npm package was found to contain malware. According to the GitHub Security Advisory (GHSA-8m82-6fp4-38m4), any computer with this package installed or running should be considered fully compromised.\n\nImmediate action is required: all secrets and keys stored on affected computers must be rotated from a different, uncompromised system. While the package should be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the package installation, as the attacker may have gained full control of the system.\n\nThe advisory was published on 2026-08-24 via GitHub's security advisory system.
Indicators of compromise
- Packages
- conversa-sdk
Remediation
- Immediately rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the conversa-sdk package from all affected systems
- Conduct a full security audit and malware scan of any system that had conversa-sdk installed
- Review system logs and access patterns for any unauthorized activity during the period the package was installed
- Consider the affected systems as potentially fully compromised and plan for reimaging if critical infrastructure
Sources
- GitHub Advisory GHSA-8m82-6fp4-38m4 · GitHub Advisory Database
Cite this entry
"Malware in conversa-sdk." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 24, 2026; last updated August 24, 2026. https://supplychainattack.org/incident/malware-in-conversa-sdk-wa1fzi
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malicious code in sm-session (npm)
The npm package sm-session (version 99.0.1) contains malicious preinstall and postinstall lifecycle scripts that beacon to a hardcoded IP address (16.192.173.5) over plain HTTP, exfiltrating installer host information. This is a dependency-confusion reconnaissance attack designed to identify which environments resolve the package name.
npmCompromised packageDependency confusion - containedcritical
Malicious code in sm-apikey-model (npm)
The npm package sm-apikey-model versions 99.0.0 and 99.0.1 contain malicious preinstall and postinstall lifecycle scripts that exfiltrate installation telemetry to a hardcoded IP endpoint. The package exhibits characteristics of a dependency-confusion reconnaissance probe.
npmCompromised packageDependency confusion - containedcritical
Malicious code in message-compiler (npm)
The npm package message-compiler is a typosquat of @intlify/message-compiler containing malicious code that exfiltrates installer environment variables, public IP, and hostname via preinstall script execution.
npmTyposquattingCompromised package - activecritical
Malicious code in sm-billing-form (npm)
Malicious npm package sm-billing-form (versions 99.0.0 and 99.0.1) contains preinstall and postinstall lifecycle scripts that execute curl commands to a hardcoded IP address (16.192.173.5) over cleartext HTTP, exfiltrating install environment details. The high version number and behavior pattern indicate a dependency-confusion attack targeting internal packages of the same name.
npmCompromised packageDependency confusion