Which versions of @vampirchik147/libxmljs2 are malicious?

The following npm versions of @vampirchik147/libxmljs2 are flagged malicious: 0.19.7. Treat any of these as compromised.

How do I remediate @vampirchik147/libxmljs2 if I installed it?

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

If @vampirchik147/libxmljs2 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 @vampirchik147/libxmljs2 part of a known attack campaign?

Yes — @vampirchik147/libxmljs2 is associated with the RLMA-2026-01074 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 @vampirchik147/libxmljs2 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @vampirchik147/libxmljs2 (version 0.19.7).

Malicious package

@vampirchik147/libxmljs2npm

Advisory published Mar 18, 2026Updated Mar 23, 2026

@vampirchik147/libxmljs2 is a confirmed malicious npm package (MAL-2026-1643) that executes malicious code on install (malicious version 0.19.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @vampirchik147/libxmljs2 (npm)

MAL-2026-1643

Immediate action

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

npm uninstall @vampirchik147/libxmljs2

What this malware does

The package @vampirchik147/libxmljs2 was found to contain malicious code.

Malicious versions

1 flagged

0.19.7

Indicators of compromise (SHA-256)

d4870086853f586d5fff5ec848235dd16b8d2e5c224d0e43990b0dce09ba2c34

6f1f47e6141b6c2d1af00b86d33d71cac6c53f6e64f307e1533e4ae108560092

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01074

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @vampirchik147/libxmljs2-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