UTC

Fake n8n community nodes

Malicious npm packages posed as n8n community nodes, most as a Google Ads integration. Once installed, they read the OAuth credentials stored in n8n when a workflow ran and sent them to the attacker.

First seen
2026-01-06
Disclosed
2026-01-09
Affected packages
9
Attributed to
No public attribution

What to do

Uninstall the nodes, then revoke and rotate the OAuth tokens and API keys stored in affected n8n instances: stolen tokens keep working after the package is gone. Prefer verified nodes, and on self-hosted instances that need none, turn community nodes off.

Check a lockfile for these releases →
Affected releases
PackageRegistryVersions
n8n-nodes-hfgjf-irtuinvcm-lasdqewriitnpmall versions
n8n-nodes-gg-udhasudsh-hgjkhg-officialnpmall versions
n8n-nodes-ggdv-hdfvcnnje-uyrokvbklnpmall versions
n8n-nodes-vbmkajdsa-uehfitvv-ueqjhhhksdlkkmznpmall versions
n8n-nodes-performance-metricsnpmall versions
n8n-nodes-gasdhgfuy-rejerw-ytjsadxnpmall versions
n8n-nodes-danevReported by Endor Labs; no OSV recordnpm1.2.9 to 3.5.3
n8n-nodes-rooyai-modelReported by Endor Labs; no OSV recordnpm1.0.1 to 1.0.25
n8n-nodes-zalo-viettsReported by Endor Labs; no OSV recordnpm3.0.1 and later

Written up from the sources above and last checked on 2026-11-18. ShieldMap describes what was affected and what to do; it does not publish the malicious code or how it worked. Report a correction to [email protected].