DependencyWatch.io
FeedSolutionsSubmitScan your lockfile
Criticalnpm28 affected versions

newtun

newtun has 28 versions 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 newtun.

  • newtun@1.0.27
  • newtun@1.0.26
  • newtun@1.0.25
  • newtun@1.0.24
  • newtun@1.0.23
  • newtun@1.0.22
  • newtun@1.0.21
  • newtun@1.0.20
  • newtun@1.0.19
  • newtun@1.0.18
  • newtun@1.0.17
  • newtun@1.0.16
  • newtun@1.0.15
  • newtun@1.0.14
  • newtun@1.0.13
  • newtun@1.0.12
  • newtun@1.0.11
  • newtun@1.0.10
  • newtun@1.0.9
  • newtun@1.0.8
  • newtun@1.0.7
  • newtun@1.0.6
  • newtun@1.0.5
  • newtun@1.0.4
  • newtun@1.0.3
  • newtun@1.0.2
  • newtun@1.0.1
  • newtun@1.0.0

The incident that flagged it

Critical

GitHub Advisory npm CWE-506 sweep - 2026-08-11 batch (webhook.site Web3 typosquat credential-theft ring `@openzeppelin-4/5/contracts`+`@aerodrome-finance/contracts`+`@aerodrome-finance/slipstream`+`ethereum-vault-connector`, `safe-local-env-loader` env-local RAT sibling, `newtun` unencrypted-WebSocket PTY RAT with self-update, `svelte-vim-kit`+`kit-vim-map` map-streak-kit family continuation, `@nzeros/codebreak` Go ELF disguised as C solver, `base65-*` base-x typosquat cluster with 123KB obfuscated payload + `bs58-*` boilerplate siblings, coordinated `oastify.com`/`sslip.io`/webhook OAST dep-confusion recon beacons)

38 npm CWE-506 advisories published 2026-08-11. Headline: five-package Web3 typosquat ring (@openzeppelin-4/contracts, @openzeppelin-5/contracts, @aerodrome-finance/contracts, @aerodrome-finance/slipstream, ethereum-vault-connector) sharing the same webhook.site credential-exfil TTP with 60-240s detached-process delay + sandbox evasion, safe-local-env-loader continuing the 2026-08-10 env-local Windows RAT, and newtun shipping a PTY reverse shell with self-update.

Versions named here: 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.8, 1.0.9, 1.0.10, 1.0.11, 1.0.12, 1.0.13, 1.0.14, 1.0.15, 1.0.16, 1.0.17, 1.0.18, 1.0.19, 1.0.20, 1.0.21, 1.0.22, 1.0.23, 1.0.24, 1.0.25, 1.0.26, 1.0.27

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. 1.Rotate every credential that machine or CI job could reach - registry tokens, cloud keys, SSH keys, CI secrets - from a different machine.
  2. 2.Pin to a version not listed above, then reinstall from a clean lockfile.
  3. 3.Clear caches and private mirrors. Artifactory, Nexus, Verdaccio, and devpi routinely keep serving a tarball after the public registry has pulled it.
  4. 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

newtun 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 newtun 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.