---
-= Per source details. Do not edit below this line.=-
Source: ghsa-malware (63e80eb984d70eca3cfadd2c9872df353dba45f0c14111f84c9c0ab34f8b8930)
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Source: ossf-package-analysis (dff83480baa83847cecc2872e140ba12c989ff70f00e2d4208bdcac4f9cf6f39)
The OpenSSF Package Analysis project identified 'rambox' @ 1.0.0 (npm) as malicious.
It is considered malicious because:
• The package executes one or more commands associated with malicious behavior.
mitre ttp
T1195.001
// versions and what to do
Malicious
all versions
Clean
none confirmed
Remove it from every machine and lockfile it reached. Treat any credentials, tokens and SSH keys present on those machines as exposed and rotate them. Check CI runners and container images that installed it.
There is a stored XSS in Rambox 0.6.9 that can lead to code execution. The XSS is in the name field while adding/editing a service. The problem occurs due to incorrect sanitization of the name field when being processed and stored. This allows a user to craft a payload for Node.js and Electron, such as an exec of OS commands within the onerror attribute of an IMG element.
// cvss v3.1 vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High
Checked 2026-10-04 at 01:10 UTC. The most recent advisory here was published 2022-05-24. Updated continuously from NVD, GHSA, OSV and CNA feeds.