Skip to content
supplychainattack.orgSupply chain attack incident catalog
activecritical

Malware in @vaultflow/update-flow

Malware was discovered in the npm package @vaultflow/update-flow. 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
  • @vaultflow/update-flow

A malicious package named @vaultflow/update-flow was published to npm and contains malware. According to the GitHub Advisory (GHSA-gv55-mvjq-232h), 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 there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the compromise.\n\nThis represents a critical supply chain attack through a malicious npm package with full system compromise capabilities.

Indicators of compromise

Packages
  • @vaultflow/update-flow

Remediation

  • Immediately remove @vaultflow/update-flow from all systems
  • Rotate all secrets, API keys, and credentials from a different, uncompromised computer
  • Assume full system compromise and consider rebuilding affected systems from clean media
  • Audit all systems for signs of unauthorized access or additional malware
  • Review logs for any suspicious activity during the period the package was installed

Sources

  1. GitHub Advisory GHSA-gv55-mvjq-232h · GitHub Advisory Database

Cite this entry

"Malware in @vaultflow/update-flow." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 28, 2026; last updated July 28, 2026. https://supplychainattack.org/incident/malware-in-vaultflow-update-flow-xrwwhp

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