Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in @nasdtickets/common

Malware was discovered in the npm package @nasdtickets/common. Systems with this package installed are considered fully compromised and require immediate remediation.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with @nasdtickets/common installed
Ecosystems
Attack vectors
Affected entities
  • @nasdtickets/common

A malware incident was identified in the npm package @nasdtickets/common, published via GitHub Advisory GHSA-49j5-8rcw-8rh8 on August 6, 2026.\n\nAny computer with this package installed or running should be considered fully compromised. The malware grants full control of affected systems to an outside entity, creating a critical risk to all secrets and keys stored on those machines.\n\nImmediate action is required: all secrets and keys should be rotated from a different, unaffected computer. While the package can be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the initial compromise.

Indicators of compromise

Packages
  • @nasdtickets/common

Remediation

  • Immediately remove @nasdtickets/common from all systems
  • Rotate all secrets, API keys, and credentials from a separate, unaffected computer
  • Audit system logs for unauthorized access or activity
  • Consider the affected system(s) fully compromised and perform forensic analysis
  • Scan systems for additional malware or persistence mechanisms
  • Review and revoke any access tokens or credentials that may have been exposed

Sources

  1. GitHub Advisory GHSA-49j5-8rcw-8rh8 · GitHub Advisory Database

Cite this entry

"Malware in @nasdtickets/common." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 6, 2026; last updated August 6, 2026. https://supplychainattack.org/incident/malware-in-nasdtickets-common-10g8z6

Suggest a correction

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

  1. containedcritical

    Malicious code in 3-buildsight-web (npm)

    The npm package 3-buildsight-web contains malicious code that fetches and executes arbitrary JavaScript from a remote Bitbucket URL on module load, granting full page privileges to an unverified third party.

    npmCompromised package
  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 create-coin (npm)

    create-coin@20.1.1 on npm contained malicious postinstall code that collected sensitive environment variables, credentials, and host reconnaissance data. The package impersonated an esbuild platform build and exfiltrated data to a hardcoded endpoint.

    npmCompromised packageTyposquatting
  4. resolvedcritical

    Malicious code in @syncraft-labs/vue (npm)

    The npm package @syncraft-labs/vue version 0.4.1 contained malicious obfuscated code in its ESM build that implements a blockchain-hosted C2 dropper (EtherHiding pattern), enabling remote code execution on any consumer importing the package.

    npmCompromised package