Which versions of libxmlfinal4 are malicious?

The following npm versions of libxmlfinal4 are flagged malicious: 0.30.3. Treat any of these as compromised.

How do I remediate libxmlfinal4 if I installed it?

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

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

Yes — libxmlfinal4 is associated with the RLMA-2026-01404 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 libxmlfinal4 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for libxmlfinal4 (version 0.30.3).

Malicious package

libxmlfinal4npm

Advisory published Dec 11, 2025Updated Mar 19, 2026

libxmlfinal4 is a confirmed malicious npm package (MAL-2025-192453) that executes malicious code on install (malicious version 0.30.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in libxmlfinal4 (npm)

MAL-2025-192453

Immediate action

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

npm uninstall libxmlfinal4

What this malware does

The package libxmlfinal4 was found to contain malicious code.

Malicious versions

1 flagged

0.30.3

Indicators of compromise (SHA-256)

d41a78ad1712a21fd085e3a8188b1e5522b8140cdc8b562d5ff933ceefe923f6

4b3f06b8de1375e6ce974cad4a9906d6c308f47bae27ff7e5d653ca479bdf43e

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01404

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks libxmlfinal4-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