HighAdvisory sweepnpm2 affected versions

hardhat-zet

hardhat-zet has 2 versions on the npm registry flagged in 2 incidents we track. Only the exact versions listed below were named by the source advisories.

hardhat-zet was recorded in a daily advisory sweep. The write-up groups it into a cluster with the evidence available at the time; check the cluster note before treating it as a confirmed compromise.

Affected versions

Check what you actually have installed with npm ls hardhat-zet.

hardhat-zet@2.0.1
hardhat-zet@1.0.0

The 2 incidents that flagged it

High3 Oct 2026

GitHub Advisory malware sweep - 2026-10-02 (late) + 2026-10-03 (npm `amel10` AWS API Gateway dep-confusion mass push targeting Amazon/Alexa internal names - 6 confirmed packages sharing C2 `s85r5k14qk.execute-api.us-east-1.amazonaws.com`: `alexa-cybertron-team-code-review-agent`, `okra-cloud-cdk`, `ai-workshop-radio-app`, `ai-workshop-maa15-radio`, `ai-workshop-radio-lambda`, `niksinnkatalapp`; 5 npm PhantomSub Baileys silent WhatsApp follow siblings `mikuhostt-baileys`, `luoxy-baileys`, `@zanta/baileys`, `wailib`, `prastzy`; pip `dedh-devops-automation` AWS Lambda + Secrets Manager credential theft `spo365-graph` family continuation; pip `voxeval` cryptominer NEW campaign `2026-10-voxeval`; 2 Go module `Graphalgo` campaign expansion `gogets.dev/btreex`, `gocommunity.io/orderedbtree`; npm `@bluewin/utils` Burp-Collaborator Swisscom-scope dep-confusion probe by `securityresearch1`; npm `@smwebserver/static@99.9.1` sentinel-version malicious-domain beacon; 9 npm CWE-506 boilerplate takedowns `turbo-ws`, `hardhat-zet`, `ui-base-colors`, `translate-base-font`, `ui.dist.min.js`, `@woodpecker-web-shared/components`, `bnppf-flag-icons`)

GHSA 2026-10-02 (late) + 2026-10-03: ~26 new advisories. Confirmed payloads: 6-package amel10 npm dep-confusion mass push against Amazon/Alexa internal names (shared C2 s85r5k14qk.execute-api.us-east-1.amazonaws.com); 5 PhantomSub Baileys siblings (query ID 7871414976211147); pip dedh-devops-automation AWS Lambda credential theft (spo365-graph family day 2); pip voxeval cryptominer; 2 Go modules in the Graphalgo campaign.

Versions named here: 1.0.0

High29 Sept 2026

GitHub Advisory malware sweep - 2026-09-28 (late) + 2026-09-29 (donutautosellsrc campaign extends to pip `aseitylab` day 3; npm `hardhat-` pino-impersonator Ethereum-dev lure; npm `nebula-` Windows `.kntrat` RAT dropper family; npm `fabric-*` Minecraft credential stealer via Discord webhook; npm `chalk-figlet` family Windows RuntimeBroker.exe dropper; npm `dotenv`-lookalike JPEG-EXIF steganography → PowerShell chain; npm `simple-date-formatter-new-12` OAST SSRF probe)

GHSA 2026-09-28 (late) + 2026-09-29: 26 new advisories - 25 npm + 1 pip. Cluster A extends the donutautosellsrc Polygon-blockchain-C2 pip campaign to aseitylab (day 3, 6 packages now under wallet 0x9c0a507300fd902787bb193d80fca5ce6e1bff9a). Clusters B-F are four distinct npm operators active in the window: hardhat pino-impersonator, nebula-* Windows .kntrat RAT, fabric-* Minecraft-credential Discord-webhook stealer, chalk-figlet RuntimeBroker.exe dropper. Cluster K is 4 npm CWE-506 boilerplate takedowns with no analysis.

Versions named here: 2.0.1

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

hardhat-zet 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 hardhat-zet 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.