Which versions of libxmlfinal5 are malicious?

Every published version of libxmlfinal5 on npm is considered malicious. Remove the package entirely.

How do I remediate libxmlfinal5 if I installed it?

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

If libxmlfinal5 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.

How do I find libxmlfinal5 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for libxmlfinal5 (all published versions).

Malicious package

libxmlfinal5npm

Advisory published Dec 11, 2025Updated Dec 11, 2025

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

Malicious code in libxmlfinal5 (npm)

MAL-2025-192454

Immediate action

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

npm uninstall libxmlfinal5

What this malware does

The package libxmlfinal5 was found to contain malicious code.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

e75640235a927670445888fa0c679048cdc7ebe626bc9e046817570b83669cc3

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder

Detect & block this

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