Which versions of cfruitmaliciousxmlparser are malicious?

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

How do I remediate cfruitmaliciousxmlparser if I installed it?

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

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

Yes — cfruitmaliciousxmlparser is associated with the GHSA-8g6q-xxph-xhc9, RLMA-2026-01142 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 cfruitmaliciousxmlparser 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 cfruitmaliciousxmlparser (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 cfruitmaliciousxmlparser across your stack and pipelines.

Malicious package

cfruitmaliciousxmlparsernpm

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

MAL-2025-192546

Immediate action

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

npm uninstall cfruitmaliciousxmlparser

What this malware does

The package cfruitmaliciousxmlparser 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)

4c839905fe1bdbd371684c1b19db32c6f7ee7ce1888d2881a2c82e8507cbfc97

2e5eaaf8ade83c339f3b0892ac216af2a8acd0ff78ba33498568eae45f6cf905

cb84154af8e4b570b1b0a5ad818796e7a12c0f1a6c0cbf69bab2f17e584b0d22

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 cfruitmaliciousxmlparser (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 cfruitmaliciousxmlparser across your stack and pipelines.
If you installed it — respond
Remove cfruitmaliciousxmlparser 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 cfruitmaliciousxmlparser 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 cfruitmaliciousxmlparser 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. cfruitmaliciousxmlparser 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-8g6q-xxph-xhc9RLMA-2026-01142

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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