Which versions of 3952955c8e968410 are malicious?

The following npm versions of 3952955c8e968410 are flagged malicious: 0.9.4-ea.28. Treat any of these as compromised.

How do I remediate 3952955c8e968410 if I installed it?

Remove 3952955c8e968410 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 3952955c8e968410 — how do I know if it already compromised me?

If 3952955c8e968410 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 3952955c8e968410 part of a known attack campaign?

Yes — 3952955c8e968410 is associated with the RLMA-2025-00586, RLUA-2026-05953 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 3952955c8e968410 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for 3952955c8e968410 (version 0.9.4-ea.28).

Malicious package

3952955c8e968410npm

Advisory published Mar 3, 2025Updated Sep 1, 2026

3952955c8e968410 is a confirmed malicious npm package (MAL-2025-1682) that executes malicious code on install (malicious version 0.9.4-ea.28). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in 3952955c8e968410 (npm)

MAL-2025-1682

Immediate action

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

npm uninstall 3952955c8e968410

Malicious versions

1 flagged

0.9.4-ea.28

Indicators of compromise (SHA-256)

af4b46d56b6a3ff36ce41a3b3fe892cdb9f67686d701e41ca6cec021e0826bf2

05624a503bbe31cde784000bde1b02aa213912ed628fbda3028797dfc9b6b849

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-00586RLUA-2026-05953

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks 3952955c8e968410-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