Skip to content
supplychainattack.orgSupply chain attack incident catalog
activecritical

Malware in package-uploader

Malware discovered in the npm package package-uploader. 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
  • package-uploader

The npm package package-uploader 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. The package should be removed, though complete removal of all malicious software cannot be guaranteed due to the potential for full system compromise.\n\nThis is a critical supply chain incident affecting the npm ecosystem, with the attack vector being a compromised package distributed through the npm registry.

Indicators of compromise

Packages
  • package-uploader

Remediation

  • Immediately remove the package-uploader package from all systems
  • Rotate all secrets, API keys, and credentials from a different, uncompromised computer
  • Perform a full security audit and malware scan of affected systems
  • Review system logs for unauthorized access or activity
  • Consider the affected system(s) as potentially fully compromised and plan for complete rebuild if critical systems are involved

Sources

  1. GitHub Advisory GHSA-q8q6-p47p-ppp3 · GitHub Advisory Database

Cite this entry

"Malware in package-uploader." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 26, 2026; last updated June 29, 2026. https://supplychainattack.org/incident/malware-in-package-uploader-nfty9l

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