Which versions of elf-stats-caroling-sparkler-130 are malicious?

The following npm versions of elf-stats-caroling-sparkler-130 are flagged malicious: 2.0.0. Treat any of these as compromised.

How do I remediate elf-stats-caroling-sparkler-130 if I installed it?

Remove elf-stats-caroling-sparkler-130 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 elf-stats-caroling-sparkler-130 — how do I know if it already compromised me?

If elf-stats-caroling-sparkler-130 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 elf-stats-caroling-sparkler-130 part of a known attack campaign?

Yes — elf-stats-caroling-sparkler-130 is associated with the RLMA-2026-01274 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 elf-stats-caroling-sparkler-130 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for elf-stats-caroling-sparkler-130 (version 2.0.0).

Malicious package

elf-stats-caroling-sparkler-130npm

Advisory published Dec 11, 2025Updated Mar 19, 2026

elf-stats-caroling-sparkler-130 is a confirmed malicious npm package (MAL-2025-192482) that executes malicious code on install (malicious version 2.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in elf-stats-caroling-sparkler-130 (npm)

MAL-2025-192482

Immediate action

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

npm uninstall elf-stats-caroling-sparkler-130

What this malware does

The package elf-stats-caroling-sparkler-130 was found to contain malicious code.

Malicious versions

1 flagged

2.0.0

Indicators of compromise (SHA-256)

0273bb7532f6cdf1c7cc333611b00034deb3cf79207f3b76d63a0e748b7672a5

7e53b2f5b42d93f8a70e277335bfaa7b98402b71292c7c75d47d45ada7755cb7

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for elf-stats-caroling-sparkler-130 (version 2.0.0).
If you installed it — respond
Remove elf-stats-caroling-sparkler-130 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 elf-stats-caroling-sparkler-130 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. elf-stats-caroling-sparkler-130 on npm has been identified as a malicious package (version 2.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01274

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks elf-stats-caroling-sparkler-130-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