Which versions of libxmlfinal are malicious?

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

How do I remediate libxmlfinal if I installed it?

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

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

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

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

Malicious package

libxmlfinalnpm

Advisory published Dec 11, 2025Updated Mar 19, 2026

libxmlfinal is a confirmed malicious npm package (MAL-2025-192451) 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 libxmlfinal (npm)

MAL-2025-192451

Immediate action

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

npm uninstall libxmlfinal

What this malware does

The package libxmlfinal was found to contain malicious code.

Malicious versions

1 flagged

0.30.3

Indicators of compromise (SHA-256)

b00664d7d8c2cad969c4ae81a3e41100c2d896bb0fc1eccde422b4c676e9bf9c

c260a4c542e5f6e8d9a0cef31c6958a15b68cefce5fdcaca5a9062c019aed632

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for libxmlfinal (version 0.30.3).
If you installed it — respond
Remove libxmlfinal 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 libxmlfinal 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. libxmlfinal 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-01403

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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