Skip to content
supplychainattack.orgSupply chain attack incident catalog
activecritical

Malware in @zynkit/probe

Malware discovered in the npm package @zynkit/probe. Systems with this package installed or running are considered fully compromised, with potential for complete system takeover.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with the package installed or running
Ecosystems
Attack vectors
Affected entities
  • @zynkit/probe

The npm package @zynkit/probe has been identified as containing malware. According to the GitHub advisory, any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends immediate action: all secrets and keys stored on affected computers should be rotated 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 package installation, given the potential for complete system compromise.\n\nAffected users should treat their systems as potentially under the control of an external entity and take appropriate security measures accordingly.

Indicators of compromise

Packages
  • @zynkit/probe

Remediation

  • Immediately remove @zynkit/probe from all systems
  • Rotate all secrets, API keys, and credentials from a different, uncompromised computer
  • Assume full system compromise and conduct forensic analysis
  • Monitor affected systems for signs of unauthorized access or persistence mechanisms
  • Consider rebuilding affected systems from clean media if critical infrastructure is involved

Sources

  1. GitHub Advisory GHSA-2pxg-2qw7-jff9 · GitHub Advisory Database

Cite this entry

"Malware in @zynkit/probe." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 17, 2026; last updated August 17, 2026. https://supplychainattack.org/incident/malware-in-zynkit-probe-mmlxk4

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