sirens-lament

Details

Four pirate-themed npm packages (`blackbeards-navigator`, `beusy`, `sirens-lament`, `gunpowder-ghost`) were published by the npm account `beusy` with heavily inflated version numbers (209.0.0–210.0.0), a hallmark of dependency confusion attacks. Each package contains identical malicious lifecycle scripts (`preinstall`, `install`, and `postinstall`) that run on npm install, searching the entire filesystem (up to 8 directory levels deep) for HackTheBox CTF flags matching the pattern `HTB{`. If no flags are found, the scripts collect environment variables and `/proc/1/environ` as a fallback. The collected data is base64-encoded and exfiltrated via an HTTPS GET request to an attacker-controlled ngrok tunnel (`https://7f83-194-51-113-30.ngrok-free.app`), with the package name and hostname included as query parameters. The packages have no legitimate functionality; `index.js` exports an empty object.

This package (`sirens-lament`) identifies itself as `pkg=sirens-lament` in the exfil request. All three lifecycle hooks run the same payload, ensuring execution regardless of npm lifecycle ordering.

---
_-= Per source details. Do not edit below this line.=-_

## Source: amazon-inspector (0bbd4aa6c17a69a37f660a2e68d207c7c934863bbe4008cd42ce11fc4942119a)
The package sirens-lament was found to contain malicious code.

## Source: ghsa-malware (2ffd9830870bac2afdf00af5d5c56e2701885e2e66f2a09814d4e4087e696fad)
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 (505243e234dcc2c15fba33a376390255cb450db37d0257633a91ac048910d85b)
The OpenSSF Package Analysis project identified 'sirens-lament' @ 217.0.0 (npm) as malicious.

It is considered malicious because:

- The package communicates with a domain associated with malicious activity.

- The package executes one or more commands associated with malicious behavior.

Compromised versions (10)

• 217.0.0
• 211.0.0
• 213.0.0
• 212.0.0
• 214.0.0
• 219.0.0
• 220.0.0
• 225.0.0
• 209.0.0
• 210.0.0

Any computer that installed or ran a compromised version should be considered fully compromised. Rotate every secret on that machine from a clean environment.