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

n8n-nodes-gg-udhasudsh-hgjkhg-officialnpm

Malicious code in n8n-nodes-gg-udhasudsh-hgjkhg-official (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-539
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall n8n-nodes-gg-udhasudsh-hgjkhg-official

What this malware does

The package n8n-nodes-gg-udhasudsh-hgjkhg-official was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

53 flagged
0.0.10.0.1-security0.0.20.0.30.0.40.0.50.0.60.0.70.0.90.0.100.0.110.0.120.0.130.0.140.0.150.0.160.0.170.0.180.0.190.0.200.0.210.0.220.0.230.0.240.0.250.0.260.0.270.0.280.0.290.0.300.0.320.0.330.0.340.0.350.0.360.0.370.0.390.0.400.0.430.0.440.0.460.0.470.0.480.0.490.0.500.0.510.0.520.0.530.0.540.0.550.0.560.0.570.0.58

Indicators of compromise (SHA-256)

6c8efd64fc00332d1e3e11ab7c8aa31c81284365170590f60abffaeaa1377d4a
1f177f9d8bad0a259983bc9f3e0880c59ee120b1e686e3f10b490ab0527beec3
d3972d7a89df14a86c1b1010f675a3253726ddb69c1d466bd906fc298f41f650

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for n8n-nodes-gg-udhasudsh-hgjkhg-official (53 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging n8n-nodes-gg-udhasudsh-hgjkhg-official across your stack and pipelines.

  2. If you installed it — respond

    Remove n8n-nodes-gg-udhasudsh-hgjkhg-official from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If n8n-nodes-gg-udhasudsh-hgjkhg-official 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 n8n-nodes-gg-udhasudsh-hgjkhg-official 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. n8n-nodes-gg-udhasudsh-hgjkhg-official on npm has been identified as a malicious package (versions 0.0.1, 0.0.1-security, 0.0.2, 0.0.3, 0.0.4, 0.0.5, 0.0.6, 0.0.7, and 45 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-9gwp-x3p2-fchfRLMA-2026-01439

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks n8n-nodes-gg-udhasudsh-hgjkhg-official-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.

n8n-nodes-gg-udhasudsh-hgjkhg-official (npm) malicious package — MAL-2026-539 | O3 Security