Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in velora-kit

Malware was discovered in the npm package velora-kit, resulting in full system compromise for any installation. The package should be removed immediately and all secrets and keys rotated from a different computer.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with velora-kit installed or running
Ecosystems
Attack vectors
Affected entities
  • velora-kit

A critical malware incident was identified in the npm package velora-kit. According to the GitHub Advisory (GHSA-c48p-mmxp-3g9c), 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. While the package should be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the initial compromise, given the level of system access the malware appears to have obtained.\n\nAffected users should treat their systems as potentially fully compromised and take appropriate incident response measures.

Indicators of compromise

Packages
  • velora-kit

Remediation

  • Remove the velora-kit package immediately from all affected systems
  • Rotate all secrets, API keys, and credentials from a different, uncompromised computer
  • Assume full system compromise and conduct thorough forensic analysis
  • Monitor affected systems for signs of persistent malware or backdoors
  • Consider rebuilding affected systems from clean media if critical infrastructure is involved

Sources

  1. GitHub Advisory GHSA-c48p-mmxp-3g9c · GitHub Advisory Database

Cite this entry

"Malware in velora-kit." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 18, 2026; last updated August 18, 2026. https://supplychainattack.org/incident/malware-in-velora-kit-6q6lee

Suggest a correction

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

  1. containedcritical

    Malicious code in 3-buildsight-web (npm)

    The npm package 3-buildsight-web contains malicious code that fetches and executes arbitrary JavaScript from a remote Bitbucket URL on module load, granting full page privileges to an unverified third party.

    npmCompromised package
  2. resolvedcritical

    Malicious code in @usaa-grp-personal-profile/personal-profile-common (npm)

    Malicious package @usaa-grp-personal-profile/personal-profile-common version 999.0.0 published to public npm as a dependency-confusion attack targeting an organization's internal registry. The package contains preinstall and postinstall hooks that exfiltrate hostname, username, and working directory to an attacker-controlled OAST endpoint on every install.

    npmDependency confusionCompromised package
  3. resolvedcritical

    Malicious code in create-coin (npm)

    create-coin@20.1.1 on npm contained malicious postinstall code that collected sensitive environment variables, credentials, and host reconnaissance data. The package impersonated an esbuild platform build and exfiltrated data to a hardcoded endpoint.

    npmCompromised packageTyposquatting
  4. resolvedcritical

    Malicious code in @syncraft-labs/vue (npm)

    The npm package @syncraft-labs/vue version 0.4.1 contained malicious obfuscated code in its ESM build that implements a blockchain-hosted C2 dropper (EtherHiding pattern), enabling remote code execution on any consumer importing the package.

    npmCompromised package