Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in autotel-vitest

Malware was discovered in the npm package autotel-vitest. Any computer with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different system.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with the package installed or running
Ecosystems
Attack vectors
Affected entities
  • autotel-vitest

The npm package autotel-vitest was found to contain malware. According to the GitHub Advisory (GHSA-2x3q-hrjf-x554), any system that has installed or executed this package should be treated as fully compromised.\n\nImmediate action is required: all secrets, keys, and credentials stored on affected systems must be rotated from a different, uncompromised computer. While the malicious package should be removed, there is no guarantee that removal will eliminate all malicious software that may have been deployed during the compromise, as the attacker may have gained full control of the system.\n\nThis is a critical supply chain incident affecting the npm ecosystem.

Indicators of compromise

Packages
  • autotel-vitest

Remediation

  • Immediately rotate all secrets, keys, and credentials from a different, uncompromised computer
  • Remove the autotel-vitest package from all affected systems
  • Audit system logs and network activity for signs of unauthorized access or data exfiltration
  • Consider full system reimaging if full compromise is suspected
  • Check for any other suspicious packages or modifications on affected systems

Sources

  1. GitHub Advisory GHSA-2x3q-hrjf-x554 · GitHub Advisory Database

Cite this entry

"Malware in autotel-vitest." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 30, 2026; last updated June 30, 2026. https://supplychainattack.org/incident/malware-in-autotel-vitest-1mf3kg

Suggest a correction

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

  1. containedcritical

    Malware in chlklib

    Malware was discovered in the npm package chlklib, resulting in full system compromise of any computer with the package installed or running. All affected systems should be considered fully compromised and all secrets and keys rotated immediately from a different computer.

    npmCompromised package
  2. resolvedcritical

    Malware in alphazone

    The npm package alphazone contained malware that provided full system compromise to attackers. Any computer with the package installed or running should be considered fully compromised.

    npmCompromised package
  3. containedcritical

    Malware in chai-as-deployer

    Malware was discovered in the npm package chai-as-deployer, resulting in full system compromise for any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately from a different computer.

    npmCompromised package
  4. containedcritical

    Malware in checkout-common-tokens

    Malware was discovered in the npm package checkout-common-tokens. Systems with this package installed are considered fully compromised and require immediate remediation.

    npmCompromised package