What does the libxmljs2qwerty malware do?

The package libxmljs2qwerty was found to contain malicious code. The OpenSSF Package Analysis project identified 'libxmljs2qwerty' @ 0.30.30 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity. - The package executes one or more commands associated with malicious behavior.

Which versions of libxmljs2qwerty are malicious?

The following npm versions of libxmljs2qwerty are flagged malicious: 0.30.30. Treat any of these as compromised.

How do I remediate libxmljs2qwerty if I installed it?

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

If libxmljs2qwerty 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 libxmljs2qwerty across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for libxmljs2qwerty (version 0.30.30).

Malicious package

libxmljs2qwertynpm

Advisory published Dec 9, 2025Updated Dec 10, 2025

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

Malicious code in libxmljs2qwerty (npm)

MAL-2025-192389

Immediate action

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

npm uninstall libxmljs2qwerty

What this malware does

The package libxmljs2qwerty was found to contain malicious code.

The OpenSSF Package Analysis project identified 'libxmljs2qwerty' @ 0.30.30 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

0.30.30

Indicators of compromise (SHA-256)

2d91988ba951c71566b9b39a2279ab047bd3e9233e58720bf517d55bd2170fee

98e288816b28da06174dcb7d9315fb857fc7daf80f81a57de2fbe1b0a3419895

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

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