Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in jsontoken-extend

Malware was discovered in the npm package jsontoken-extend. Systems with this package installed should be considered fully compromised and require immediate remediation.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with jsontoken-extend installed; full system compromise possible
Ecosystems
Attack vectors
Affected entities
  • jsontoken-extendnpm package

The npm package jsontoken-extend was found to contain malware. According to the GitHub advisory (GHSA-v985-2jx7-c35g), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends that all secrets and keys stored on affected computers be rotated immediately from a different, uncompromised system. While the package should be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the compromise.\n\nThe incident was published on 2026-07-06 via the GitHub advisory system."

Indicators of compromise

Packages
  • jsontoken-extend

Remediation

  • Immediately remove the jsontoken-extend package from all affected systems
  • Rotate all secrets, API keys, and credentials stored on affected computers from a different, uncompromised system
  • Perform a full security audit and malware scan of any system that had this package installed
  • Review system logs and network traffic for signs of unauthorized access or data exfiltration
  • Consider the affected system(s) as potentially fully compromised and plan for complete rebuild if critical infrastructure

Sources

  1. GitHub Advisory GHSA-v985-2jx7-c35g · GitHub Advisory Database

Cite this entry

"Malware in jsontoken-extend." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 6, 2026; last updated July 6, 2026. https://supplychainattack.org/incident/malware-in-jsontoken-extend-usdl02

Suggest a correction

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

  1. 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
  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. activecritical

    Malware in @sdgdfgdfhhhfd/multiviewr

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

    npmCompromised package
  4. 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