Which versions of financial-utils are malicious?

The following npm versions of financial-utils are flagged malicious: 1.0.0, 1.0.1, 1.0.2. Treat any of these as compromised.

How do I remediate financial-utils if I installed it?

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

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

Yes — financial-utils is associated with the RLMA-2025-04529, RLUA-2025-05794 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 financial-utils across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for financial-utils (3 malicious versions).

Malicious package

financial-utilsnpm

Advisory published Aug 28, 2025Updated Dec 2, 2025

financial-utils is a confirmed malicious npm package (MAL-2025-41562) that executes malicious code on install (malicious versions 1.0.0, 1.0.1, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in financial-utils (npm)

MAL-2025-41562

Immediate action

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

npm uninstall financial-utils

Malicious versions

3 flagged

1.0.01.0.11.0.2

Indicators of compromise (SHA-256)

86ce82a63f99171fcd16f2353bec471cd9da71854282c3ec260afe61b9f2a09b

36de018ee5404157088232135d0394284a773aa4c58e41add670fda6833431e8

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for financial-utils (3 malicious versions).
If you installed it — respond
Remove financial-utils 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 financial-utils 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. financial-utils on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-04529RLUA-2025-05794

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks financial-utils-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