Which versions of libxmljs2woter are malicious?

The following npm versions of libxmljs2woter are flagged malicious: 0.30.4, 0.46.0. Treat any of these as compromised.

How do I remediate libxmljs2woter if I installed it?

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

If libxmljs2woter was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is libxmljs2woter part of a known attack campaign?

Yes — libxmljs2woter is associated with the GHSA-h63c-r25g-p7rw 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 libxmljs2woter across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for libxmljs2woter (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging libxmljs2woter across your stack and pipelines.

Malicious package

libxmljs2woternpm

Malicious code in libxmljs2woter (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192390

Immediate action

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

npm uninstall libxmljs2woter

What this malware does

The package libxmljs2woter was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

The OpenSSF Package Analysis project identified 'libxmljs2woter' @ 0.30.4 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

2 flagged

0.30.40.46.0

Indicators of compromise (SHA-256)

e245f573a85a2cbf43be7a5ba1424ef1f8f527c677f7c32646e2206b30f21720

12e32347b665179717e6c225ce366c1e18eecfa835a094c23674f5e5fecb705c

bb0d4800be662e443c5452e2dbf7088498563ea91fe9056e186e8e6f5d397c89

5b498dbda523b62755dd841fc0e66d62bddb3feef9c4ca0d5078b7dec40fdd1c

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for libxmljs2woter (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging libxmljs2woter across your stack and pipelines.
If you installed it — respond
Remove libxmljs2woter 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 libxmljs2woter was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks libxmljs2woter before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. libxmljs2woter on npm has been identified as a malicious package (versions 0.30.4, 0.46.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-h63c-r25g-p7rw

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

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