Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in @43uh3ig43/telemetry-client

Malware was discovered in the npm package @43uh3ig43/telemetry-client. Systems with this package installed are considered fully compromised and require immediate remediation.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with the package installed or running
Ecosystems
Attack vectors
Affected entities
  • @43uh3ig43/telemetry-client

A malicious npm package, @43uh3ig43/telemetry-client, was identified and published on GitHub's advisory database. The package contains malware that grants full control of affected systems to an outside entity.\n\nAny computer with this package installed or running should be considered fully compromised. The advisory recommends immediate rotation of all secrets and keys from a different, unaffected computer. While the package should be removed, complete removal of all malicious software cannot be guaranteed due to the level of system compromise.\n\nThe incident was disclosed via GitHub Security Advisory GHSA-hqc4-gwfr-49r6 on 2026-07-07.

Indicators of compromise

Packages
  • @43uh3ig43/telemetry-client

Remediation

  • Immediately rotate all secrets, keys, and credentials from a different, unaffected computer
  • Remove the @43uh3ig43/telemetry-client package from all affected systems
  • Conduct a full security audit and forensic analysis of any system that had this package installed
  • Monitor affected systems for signs of persistent malware or unauthorized access
  • Review and revoke any credentials or access tokens that may have been exposed

Sources

  1. GitHub Advisory GHSA-hqc4-gwfr-49r6 · GitHub Advisory Database

Cite this entry

"Malware in @43uh3ig43/telemetry-client." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 7, 2026; last updated July 7, 2026. https://supplychainattack.org/incident/malware-in-43uh3ig43-telemetry-client-17er8k

Suggest a correction

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

  1. containedcritical

    Malware in fetch-runtime

    Malware was discovered in the npm package fetch-runtime. Any system with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.

    npmCompromised package
  2. resolvedcritical

    Malicious code in ghazaly (npm)

    The npm package ghazaly version 99.9.0 contained malicious code that executed a postinstall hook to collect system information (hostname, current user, IP addresses) and exfiltrate it to a Burp Collaborator domain. The package exhibited dependency-confusion characteristics with a high version number and nonsense dependencies.

    npmCompromised packageDependency confusion
  3. containedcritical

    Malicious code in base65-13x (npm)

    base65-13x@5.0.2 on npm contains malicious obfuscated code disguised as a legitimate base-x library. The decode() function executes a ~123KB VM-style payload with dynamic code construction and network I/O capabilities.

    npmCompromised package
  4. containedcritical

    Malicious code in kit-vim-map (npm)

    The npm package kit-vim-map contained malicious code that executes a remote-controlled Linux ELF binary on installation, providing the attacker with arbitrary RCE, persistence, and file exfiltration capabilities. The binary beacons to C2 server 217.60.77.63 and establishes persistence via systemd user units.

    npmCompromised packageMalicious commit