Which versions of sing-fest-es-logger are malicious?

The following npm versions of sing-fest-es-logger are flagged malicious: 2025.10.20. Treat any of these as compromised.

How do I remediate sing-fest-es-logger if I installed it?

Remove sing-fest-es-logger from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed sing-fest-es-logger — how do I know if it already compromised me?

If sing-fest-es-logger 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.

Is sing-fest-es-logger part of a known attack campaign?

Yes — sing-fest-es-logger is associated with the RLMA-2025-05949 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find sing-fest-es-logger across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for sing-fest-es-logger (version 2025.10.20).

Malicious package

sing-fest-es-loggernpm

Advisory published Dec 1, 2025Updated Dec 2, 2025

sing-fest-es-logger is a confirmed malicious npm package (MAL-2025-191587) that executes malicious code on install (malicious version 2025.10.20). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in sing-fest-es-logger (npm)

MAL-2025-191587

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall sing-fest-es-logger

What this malware does

The package sing-fest-es-logger was found to contain malicious code.

Malicious versions

1 flagged

2025.10.20

Indicators of compromise (SHA-256)

1f04668019083ae2b7511199750b37ffd9ac54e58cf77d2ebea8d37d28b06f19

568dedb347f57208c9d7934b8818262beac7eba759430a41f2d3a12d23e12399

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for sing-fest-es-logger (version 2025.10.20).
If you installed it — respond
Remove sing-fest-es-logger from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If sing-fest-es-logger 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. sing-fest-es-logger on npm has been identified as a malicious package (version 2025.10.20 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05949

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks sing-fest-es-logger-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database