Criticalnpm1 affected version

@years18/n8n-nodes-utils-helper-p

@years18/n8n-nodes-utils-helper-p has 1 version on the npm registry flagged in 1 incident we track. Other versions of this package are not implicated - only the exact versions listed below were named by the source advisories.

Affected versions

Check what you actually have installed with npm ls @years18/n8n-nodes-utils-helper-p.

@years18/n8n-nodes-utils-helper-p@1.0.0

The incident that flagged it

Critical12 Aug 2026

GitHub Advisory npm CWE-506 sweep - 2026-08-12 batch (Web3 typosquat webhook.site ring day-2 `permit2`+`camelot-ammv2-`+`boring-vault`+`augustdigital-sdk`+`upshift-`, Ethereum-RPC-C2 `envpack-conf`+`tailwind-form-templates` XOR-encrypted second-stage on blockchain, `svelte-kit-vim`+`kit-map-vim` map-streak-kit day-4 continuation, `sui-gql`+`bcs-compact` Sui `@mysten/` typosquat continuation, ~50-package `@years17/18/19/20/` n8n-nodes-utils-helper red-team SSH-backdoor mass drop, `internallib_v756`/`v392` bare `/dev/tcp/10.0.74.63/4444` reverse shell, `mcp-util-helpers` webhook.site R-shell channel, `passkeys-react` Burp Collaborator OAST recon, `bb-twl-k7x2` Twilio-internal dep-confusion, `@telekom-ods/react-ui-kit` Deutsche Telekom internal-scope, `verify-cli`+`@assetshop/verify-cli` OAST recon pair, `dakumangalsingh` Java-Robot RAT with jpackage wrapper, boilerplate CWE-506 mass npm flood ~100 packages)

~160 npm CWE-506 advisories published 2026-08-12. Headline: Web3 typosquat webhook.site ring day-2 (permit2, camelot-ammv2-core/periphery, boring-vault, augustdigital-sdk, upshift-finance/config) with identical env/wallet-keystore exfil TTP as the 08-11 OpenZeppelin/Aerodrome ring; Ethereum-RPC-C2 pair (envpack-conf, tailwind-form-templates) fetching XOR-encrypted second-stage from blockchain via wallet 0xa322E5f3D311D3080e6f0121063e9aDC2490Ef1a; and a *~50-package `@years17/18/19/20/` red-team n8n mass drop** installing pwn@kali SSH backdoors.

Versions named here: 1.0.0

What to do if you installed one of these

Treat the machine as compromised rather than simply upgrading. Packages in these incidents typically execute at install time, so the payload has already run with whatever credentials were in the environment.

1.Rotate every credential that machine or CI job could reach - registry tokens, cloud keys, SSH keys, CI secrets - from a different machine.
2.Pin to a version not listed above, then reinstall from a clean lockfile.
3.Clear caches and private mirrors. Artifactory, Nexus, Verdaccio, and devpi routinely keep serving a tarball after the public registry has pulled it.
4.Read the incident write-up above - recommended actions differ per incident, and some have specific indicators of compromise worth grepping your logs for.

Check your whole project

@years18/n8n-nodes-utils-helper-p is one of many packages in these incidents, and it is usually pulled in as a transitive dependency rather than one you installed directly. Paste your package-lock.json to check every dependency at once - it runs in your browser and nothing is uploaded.

Check my package-lock.json All flagged npm packages

Other packages in the same incident

If @years18/n8n-nodes-utils-helper-p is in your tree, these are worth checking too - they were published by the same campaign.

See the full incident

Version data comes from the public advisories cited on each incident page. We list only versions those advisories name - we don't infer additional ones. Think this is wrong or incomplete? Tell us.