Which versions of fruit-malicious-xml-parser are malicious?

Every published version of fruit-malicious-xml-parser on npm is considered malicious. Remove the package entirely.

How do I remediate fruit-malicious-xml-parser if I installed it?

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

If fruit-malicious-xml-parser 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 fruit-malicious-xml-parser part of a known attack campaign?

Yes — fruit-malicious-xml-parser is associated with the GHSA-v98g-g97w-9v2m 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 fruit-malicious-xml-parser 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 fruit-malicious-xml-parser (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fruit-malicious-xml-parser across your stack and pipelines.

Malicious package

fruit-malicious-xml-parsernpm

Malicious code in fruit-malicious-xml-parser (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192550

Immediate action

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

npm uninstall fruit-malicious-xml-parser

What this malware does

The package fruit-malicious-xml-parser 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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

5da555002aa2614e3b466e1b6bf646cd26cd88dedf920ed790f208c851ad0339

c330d59c7529d320701e6ccf11a655110e1aeb7c9ad5d15c34ba10941c6343a6

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

Campaign

GHSA-v98g-g97w-9v2m

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks fruit-malicious-xml-parser-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