Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

siren-lamentnpm

Advisory published Updated

siren-lament is a confirmed malicious npm package (MAL-2025-49247) that steals credentials and exfiltrates sensitive data (malicious versions 0.0.0-stage, 2.14.822, 2.14.824…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in siren-lament (npm)

MAL-2025-49247
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall siren-lament

What this malware does

The package contains two files and declares no lifecycle scripts, remote fetches, credential reads, or network exfiltration paths. Version coordinate 0.0.0-stage and minimal file count are consistent with a placeholder or staging publish rather than a functional library. No code paths that would compromise an installer on npm install or require() were identified.

The OpenSSF Package Analysis project identified 'siren-lament' @ 2.14.827 (npm) as malicious.

It is considered malicious because:

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

Malicious versions

4 flagged
0.0.0-stage2.14.8222.14.8242.14.827

Indicators of compromise (SHA-256)

092c6ea787d7e5e30dda10413bd19dd94ef1007bec6652aa050ecd4e27acbf4f
17392eb04e4be8de6edb2a946224a1506007eada7261683e18b908e38e967c83
97d32da9c42a9d8228149ee4a7e75538a6bc87b1e34648adf4d1c5337f09476b
9f9146581b28381099b9aea208feeb40077658b468ce7897143988b86a5ec23b
66198e889b19f908f338ab5cad00c57bc95194bff8938dcf26c4a853c0b260d8

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for siren-lament (4 malicious versions).

  2. If you installed it — respond

    siren-lament is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If siren-lament was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. siren-lament on npm has been identified as a malicious package (versions 0.0.0-stage, 2.14.822, 2.14.824, 2.14.827 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-022287

References

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks siren-lament-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

siren-lament (npm) malicious package — MAL-2025-49247 | O3 Security