Which versions of gaarf-node-bq are malicious?

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

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

gaarf-node-bq is a typosquat — you almost certainly intended a legitimately-named package. Remove gaarf-node-bq, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

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

If gaarf-node-bq was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is gaarf-node-bq part of a known attack campaign?

Yes — gaarf-node-bq is associated with the IN-MAL-2026-018340 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-bq across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for gaarf-node-bq (version 1.0.0).

Malicious package

gaarf-node-bqnpm

gaarf-node-bq is a confirmed malicious npm package (MAL-2026-14239) that typosquats a legitimate package to trick installs (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in gaarf-node-bq (npm)

MAL-2026-14239

Immediate action

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

npm uninstall gaarf-node-bq

What this malware does

gaarf-node-bq is a dependency-confusion / typosquat canary targeting the internal google/ads-api-report-fetcher (gaarf) package. The bin entry is an empty noop and the package ships no real functionality. Its postinstall lifecycle script collects host identifiers (os.hostname(), platform, arch, node version, package name, npm lifecycle event) and POSTs them as JSON to the hardcoded endpoint https://yu7pug2j.instances.poc.jchunt.top/gaarf-node-bq. Any installer that mis-resolves the private name to the public registry has its host metadata sent to that endpoint without consent at install time.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

1f61e7b586146a833e50d74ccdff68942b4514f66c38beca981d2ead87761633

Detection & response playbook

Typosquat

Find it
Search your lockfiles and build artifacts for gaarf-node-bq (version 1.0.0).
If you installed it — respond
gaarf-node-bq is a typosquat — you almost certainly intended a legitimately-named package. Remove gaarf-node-bq, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If gaarf-node-bq was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. gaarf-node-bq 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-018340

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks gaarf-node-bq-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

Explore

All malware advisories How O3 detects malware Vulnerability database