Skip to content
supplychainattack.orgSupply chain attack incident catalog
resolvedcritical

Malicious code in @assetshop/verify-cli (npm)

The npm package @assetshop/verify-cli contained malicious code in its preinstall hook that collected and exfiltrated system and user information to an external OAST callback domain. The package exhibited the standard dependency-confusion reconnaissance pattern targeting private registries.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any organization installing @assetshop/verify-cli from npm; reconnaissance data exfiltrated for internal network mapping.
Ecosystems
npm
Attack vectors
Compromised packageDependency confusion
Affected entities
  • @assetshop/verify-clinpm package with malicious preinstall hook

The npm package @assetshop/verify-cli was found to contain malicious code executed during installation via a preinstall hook. Upon npm install, the package's index.js collected sensitive host and installer identity information including username (via whoami), hostname, platform, architecture, current working directory, home directory, and Node version.\n\nThe collected data was transmitted to a hardcoded Interactsh/OAST callback subdomain at 5f8a1ed70fb7761d678agw9bapayyyyyb.oast.site via HTTPS GET requests with values embedded in the URL path, and via DNS lookups to ${user}.${hostname}.assetshop-verify-cli. This behavior is consistent with the standard dependency-confusion reconnaissance pattern used to probe for internal name resolution against private package registries.\n\nThe malicious package was identified by Amazon Inspector and credited to the OpenSSF malicious-packages repository. The attack demonstrates a supply chain compromise targeting organizations that may have internal packages with similar naming conventions in private registries.

Indicators of compromise

Packages
  • @assetshop/verify-cli
Domains
  • 5f8a1ed70fb7761d678agw9bapayyyyyb.oast.site

Remediation

  • Immediately uninstall @assetshop/verify-cli from all systems and environments
  • Audit npm install logs and package-lock.json files to identify when and where the package was installed
  • Assume any system that installed this package has had its hostname, username, and internal network information exposed; review network access logs for connections to 5f8a1ed70fb7761d678agw9bapayyyyyb.oast.site and related DNS queries
  • Review private registry access logs for any suspicious activity following installation of this package
  • Implement package name allowlisting and private registry-first resolution policies to prevent dependency confusion attacks
  • Monitor for similar malicious packages in the @assetshop scope and related naming patterns

Sources

  1. GitHub Advisory GHSA-9vm3-xhgh-q4pr · GitHub Advisory Database

Cite this entry

"Malicious code in @assetshop/verify-cli (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 12, 2026; last updated August 12, 2026. https://supplychainattack.org/incident/malicious-code-in-assetshop-verify-cli-npm-tv3sym

Suggest a correction

Found an error or have a newer source? Corrections to factual errors take priority over new entries.

Related incidents

  1. containedcritical

    Malicious code in stillm4ddpocs-demo-sprocket (npm)

    The npm package stillm4ddpocs-demo-sprocket version 999.9.12 contains malicious code that exfiltrates system and project metadata via multiple channels (HTTPS, HTTP, and DNS) to a hardcoded callback host. The package uses a high version number to exploit dependency-confusion attacks against organizations with internal packages of the same name.

    npmCompromised packageDependency confusion
  2. resolvedcritical

    Malicious code in @usaa-grp-personal-profile/personal-profile-common (npm)

    Malicious package @usaa-grp-personal-profile/personal-profile-common version 999.0.0 published to public npm as a dependency-confusion attack targeting an organization's internal registry. The package contains preinstall and postinstall hooks that exfiltrate hostname, username, and working directory to an attacker-controlled OAST endpoint on every install.

    npmDependency confusionCompromised package
  3. resolvedcritical

    Malicious code in lumen-pages-community (npm)

    lumen-pages-community@9.9.9 on npm contains malicious code that executes a postinstall hook to exfiltrate installer metadata (hostname, username, working directory, platform, Node version, CI environment, npm user-agent) to a hardcoded webhook.site URL. The high version number and lack of functionality suggest a dependency-confusion attack.

    npmCompromised packageDependency confusion
  4. resolvedcritical

    Malicious code in @gfe/lx-watcher (npm)

    The npm package @gfe/lx-watcher contained malicious code that exfiltrated host metadata (hostname, OS username, working directory, timestamp) via npm lifecycle hooks to a hardcoded webhook.site endpoint. The package exploited dependency confusion by using a scoped name (@gfe/*) with a no-op stub, allowing silent resolution against the public registry while leaking host identifiers.

    npmDependency confusionCompromised package