Which versions of gaarf-node are malicious?

The following npm versions of gaarf-node are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate gaarf-node if I installed it?

gaarf-node establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed gaarf-node — how do I know if it already compromised me?

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

Yes — gaarf-node is associated with the IN-MAL-2026-018339 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 gaarf-node 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 gaarf-node (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging gaarf-node across your stack and pipelines.

Malicious package

gaarf-nodenpm

gaarf-node is a confirmed malicious npm package (MAL-2026-14238) that opens a backdoor for remote access (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in gaarf-node (npm)

MAL-2026-14238

Immediate action

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

npm uninstall gaarf-node

What this malware does

The package's postinstall script runs automatically on npm install and collects host identifiers (os.hostname(), platform, arch, node version, package name, npm lifecycle event) and POSTs them as JSON to the hardcoded remote host ze0buq23.instances.poc.jchunt.top at path /gaarf-node. The package name impersonates Google's ads-api-report-fetcher (gaarf) project referenced in source.txt, while package.json self-labels as a Security research canary. The destination domain is unrelated to the impersonated Google project, and the outbound beacon fires with no user consent as a lifecycle side effect of installation.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

fc539c4e835f015b5f7b9e65ca33a720e44ee0191e3bbf422085949e5d3029b9

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for gaarf-node (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging gaarf-node across your stack and pipelines.
If you installed it — respond
gaarf-node establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If gaarf-node 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 gaarf-node 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. gaarf-node on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018339

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks gaarf-node-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database