Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@activepieces/piece-google-bigquerynpm

@activepieces/piece-google-bigquery is a confirmed malicious npm package (MAL-2026-13394) that steals credentials and exfiltrates sensitive data (malicious version 0.0.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @activepieces/piece-google-bigquery (npm)

MAL-2026-13394
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @activepieces/piece-google-bigquery

What this malware does

src/index.js combines child_process invocation, execution of network reconnaissance commands (ping), and HTTP POST calls in a package that presents itself as a Google BigQuery integration for Activepieces. The BigQuery piece would normally interact only with Google's BigQuery REST APIs via the official SDK; there is no legitimate reason for this module to spawn OS commands such as ping and POST results to an external endpoint. The pattern is consistent with a typosquat/lookalike of the legitimate Activepieces BigQuery piece performing host reconnaissance and data exfiltration on load.

Malicious versions

1 flagged
0.0.6

Indicators of compromise (SHA-256)

697ef2a7cda3bcaad9ed5938e7b59f66c74a49bbeede863d21b530988bca2f13

Detection & response playbook

Credential / info stealer

  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @activepieces/piece-google-bigquery (version 0.0.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @activepieces/piece-google-bigquery across your stack and pipelines.

  2. If you installed it — respond

    @activepieces/piece-google-bigquery is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If @activepieces/piece-google-bigquery 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.

  4. How O3 protects you

    O3 blocks @activepieces/piece-google-bigquery 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. @activepieces/piece-google-bigquery on npm has been identified as a malicious package (version 0.0.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-016277

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @activepieces/piece-google-bigquery-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database