NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

@activepieces/piece-google-bigquerynpm

Advisory published Updated

@activepieces/piece-google-bigquery is a confirmed malicious npm package (MAL-2026-13394) that steals credentials and exfiltrates sensitive data (malicious versions 0.0.5, 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

The package presents itself as an Activepieces connector for Google BigQuery but src/index.js combines require("child_process"), an OS reconnaissance command (ping), and multiple POST calls to an external endpoint at module load. This is the network-command-exfiltration + hardcoded-C2 shape rather than a BigQuery client: a legitimate BigQuery piece would call googleapis / @google-cloud/bigquery, not shell out and POST host data to an unrelated destination. Loading the module therefore executes attacker-controlled behavior against the installer's host with no relation to the advertised BigQuery functionality.

Malicious versions

2 flagged
0.0.50.0.6

Indicators of compromise (SHA-256)

697ef2a7cda3bcaad9ed5938e7b59f66c74a49bbeede863d21b530988bca2f13
acc3321f587f5a8efea8256aeb935a905df2da5f5a901cd8f7355a75e3832da3

Detection & response playbook

Credential / info stealer

  1. Find it

    Search your lockfiles and build artifacts for @activepieces/piece-google-bigquery (2 malicious versions).

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

Campaign

IN-MAL-2026-016277IN-MAL-2026-016382

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
@activepieces/piece-google-bigquery (npm) malicious package — MAL-2026-13394 | O3 Security