Which versions of gfruitmaliciousxmlparser are malicious?

Every published version of gfruitmaliciousxmlparser on npm is considered malicious. Remove the package entirely.

How do I remediate gfruitmaliciousxmlparser if I installed it?

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

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

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

Malicious package

gfruitmaliciousxmlparsernpm

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

MAL-2025-192551

Immediate action

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

npm uninstall gfruitmaliciousxmlparser

What this malware does

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

6ad7c027158af15fd733f4bec44c1096737a0c28eb8d90433046b56dc5ec1bba

4813943ebd3c7e53be5309757e509dc22587aab81ded149ba9b56b37e87a4dd9

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 gfruitmaliciousxmlparser (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging gfruitmaliciousxmlparser across your stack and pipelines.
If you installed it — respond
Remove gfruitmaliciousxmlparser 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 gfruitmaliciousxmlparser 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 gfruitmaliciousxmlparser 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. gfruitmaliciousxmlparser 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-rr49-5crf-m37w

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

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