siren-lament (npm) · Malicious Code
Affects siren-lamentSource GCVE Database
Malicious package : remove siren-lament and rotate any secrets on hosts that installed it.
Data as of 29 Oct 2026, 18:11 UTC
Malicious package
Published to npm · OSV MAL-2025-49247
What to do
Remove siren-lament from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmsiren-lament | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
The npm package 'siren-lament' versions 2.14.822, 2.14.824, 2.14.827, and 0.0.0-stage have been identified as malicious by the OpenSSF Package Analysis project. The package executes commands associated with malicious behavior. However, the package contains minimal files and no lifecycle scripts or network exfiltration paths were detected. No code paths compromising the installer during npm install or require() were found.