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. resolvedcritical

    Malicious code in autbank-core (npm)

    The npm package autbank-core contained malicious preinstall and postinstall lifecycle hooks that exfiltrated environment variables, credentials, and system information to a hardcoded webhook.site endpoint during installation.

    npmCompromised package
  2. resolvedcritical

    Malicious code in adxaa (npm)

    The npm package adxaa contained obfuscated malicious JavaScript designed to target users of a specific WordPress site. The payload exfiltrates session data, deletes accounts, and hijacks credentials via email overwrite and password reset.

    npmCompromised package
  3. resolvedcritical

    Malicious code in upload-to-gcp (npm)

    upload-to-gcp@3.2.1 (npm) contains malicious code in its postinstall script that exfiltrates host identifiers to an attacker-controlled endpoint. The package masquerades as a Google Cloud Platform utility but performs unauthorized telemetry collection at install time.

    npmCompromised package
  4. resolvedcritical

    Malicious code in akamai-sensor (npm)

    A malicious npm package named akamai-sensor impersonated Akamai's legitimate sensor_data anti-bot SDK. The package contained hidden JavaScript code concealed using invisible Unicode characters and implemented a dynamic command-and-control channel via a Google Calendar dead-drop, enabling arbitrary code execution on installation.

    npmCompromised packageTyposquatting