Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

libxmljs2varabobanpm

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

MAL-2025-192388
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall libxmljs2varaboba

What this malware does

The package libxmljs2varaboba was found to contain malicious code.

The OpenSSF Package Analysis project identified 'libxmljs2varaboba' @ 0.30.2 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged
0.30.2

Indicators of compromise (SHA-256)

16ad9ea87f573dd90a31d14b711b01971c879f66ff957465239862bd69cf34c7
c5238325d9c28808a2213c9d93413847ccb8a9989720c91a2e6f8b161947fda0

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

    Remove libxmljs2varaboba 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.

  3. Did it already run?

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

  4. How O3 protects you

    O3 blocks libxmljs2varaboba 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. libxmljs2varaboba on npm has been identified as a malicious package (version 0.30.2 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 libxmljs2varaboba-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.

libxmljs2varaboba (npm) malicious package — MAL-2025-192388 | O3 Security