Malicious code in conversa-sdk (npm)

The conversa-sdk npm package versions 1.0.0, 1.0.4, 1.0.5, 1.0.6, 1.0.8, 1.0.9, 2.0.0, 2.0.2, 2.0.3, and 2.0.4 include a postinstall.js script that unconditionally reads the ~/.npmrc file, capturing npm authentication tokens, and collects system details such as OS username, hostname, Node.js version, and platform. This information is sent via an HTTP POST request to a suspicious Vercel-hosted endpoint (chatbot-lac-eight-78.vercel.app), which is unrelated to the package publisher. The package README falsely claims no network activity during installation, indicating deliberate deception. The exfiltrated npm tokens enable attackers to publish malicious packages under the victim's npm account, facilitating supply-chain compromise. The malicious behavior is confirmed by multiple sources including Amazon Inspector and GHSA malware advisories.

The compromise of npm authentication tokens allows attackers to publish malicious packages under the victim's npm account, potentially affecting any downstream users of those packages. The presence of this package on a system implies full compromise, as attackers may have gained access to secrets and keys stored on the machine. This can lead to further unauthorized access, data theft, and persistent backdoors. Removal of the package does not guarantee elimination of all malicious artifacts or access.

There is no official patch or fix available for this malicious package. Immediate mitigation requires removing the conversa-sdk package from all affected systems. All npm authentication tokens and any other secrets or keys stored on the compromised machines must be rotated immediately from a secure, uncompromised environment. Due to the high likelihood of full system compromise, a thorough incident response and forensic analysis is recommended to identify and remediate any additional malicious presence.