HighAdvisory sweepnpm1 affected version

asepxyznew

asepxyznew has 1 version on the npm registry flagged in 1 incident we track. Only the exact versions listed below were named by the source advisories.

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

asepxyznew@*

The incident that flagged it

High10 Oct 2026

GitHub Advisory malware sweep - 2026-10-10 (new `s4yhii` native-binary credential-stealer dep-confusion operator - 16 npm packages across `@galicia-toolkit-nestjs/`, `@galicia-toolkit-nestjs-20/`, `@galicia-toolkit-nestjs-20-lite/`, `@galicia-toolkit-cheques-nc/`, `@brick-v2/` loading prebuilds/-/metrics.node ELF+PE that forks+setsid and exfils AWS/GitHub/npm/Azure DevOps/Actions tokens to oob.s4yhii.com/native; `@tunstock/remact-dom@19.2.0` react-dom typosquat with confirmed `tele.metry.orgin.net/api/v1/events` beacon; Baileys/libsignal lure continuation `@fer2809fl/baileys`+`cloud-baileys`+`arsya-baileys`+10-package `asepxyz` cluster; crates.io `sharpnes` Telegram-Desktop + Chrome-extension/wallet infostealer (first cargo malware advisory this week); 3-package `kmf-` + 2-package internal-frontend dep-confusion with oast.pro OAST; 5-package `@tvg-mar/` dep-confusion probes; 2 Tailwind typosquats; plus pypi `ig-gox` Instagram abuse)

GHSA 2026-10-10: ~48 fresh malware advisories across 10 clusters (46 npm, 1 pypi, 1 crates). Headline items: new s4yhii operator native-binary credential-stealer dep-confusion cluster (16 packages across @galicia-toolkit-nestjs* and @brick-v2 scopes, prebuilds/metrics.node ELF+PE forks+setsid and exfils cloud/CI tokens to oob.s4yhii.com/native); first-seen crates.io infostealer sharpnes targeting Telegram Desktop sessions + Chrome extension/wallet data via Telegram Bot API; and @tunstock/remact-dom@19.2.0 react-dom typosquat with confirmed install-time beacon to tele.metry.orgin.net.

Versions named here: *

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

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