Which versions of efruitmaliciousxmlparser are malicious?

The following npm versions of efruitmaliciousxmlparser are flagged malicious: 0.30.1. Treat any of these as compromised.

How do I remediate efruitmaliciousxmlparser if I installed it?

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

If efruitmaliciousxmlparser 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 efruitmaliciousxmlparser part of a known attack campaign?

Yes — efruitmaliciousxmlparser is associated with the GHSA-qhw7-w9cj-645j, RLMA-2026-01270 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 efruitmaliciousxmlparser 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 efruitmaliciousxmlparser (version 0.30.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging efruitmaliciousxmlparser across your stack and pipelines.

Malicious package

efruitmaliciousxmlparsernpm

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

MAL-2025-192548

Immediate action

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

npm uninstall efruitmaliciousxmlparser

What this malware does

The package efruitmaliciousxmlparser 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.

Malicious versions

1 flagged

0.30.1

Indicators of compromise (SHA-256)

2269dbdf12da95adac478c48c4c6dfe9d20b1df297bdcbdf03b883e9725096e1

4fb4a97e8162bf9b742b086bfbd8f88bd1f2ea22facfe7ff086bdf9d5923ebd6

92b20412a6a00cae03838e535cfce7d1d8e215aa85b30582d3cc784f9890fe09

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 efruitmaliciousxmlparser (version 0.30.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging efruitmaliciousxmlparser across your stack and pipelines.
If you installed it — respond
Remove efruitmaliciousxmlparser 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 efruitmaliciousxmlparser 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 efruitmaliciousxmlparser 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. efruitmaliciousxmlparser on npm has been identified as a malicious package (version 0.30.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-qhw7-w9cj-645jRLMA-2026-01270

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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