Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in @finantix/webcomponents

Malware was discovered in the npm package @finantix/webcomponents. 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
  • @finantix/webcomponents

A malware incident was identified in the npm package @finantix/webcomponents, published as GitHub Advisory GHSA-hf7q-222g-654m on June 29, 2026.\n\nAny computer with this package installed or running should be considered fully compromised. The malware grants outside entities full control of affected systems, allowing potential exfiltration of secrets, keys, and other sensitive data.\n\nImmediate remediation requires rotating all secrets and keys from a different, uncompromised computer. While the package should be removed, complete removal of all malicious software cannot be guaranteed due to the level of system compromise achieved by the malware.\n\nUsers should assume that any credentials, API keys, or sensitive information stored on affected systems have been exposed and take appropriate action to revoke and rotate them.

Indicators of compromise

Packages
  • @finantix/webcomponents

Remediation

  • Immediately isolate any computer with @finantix/webcomponents installed from the network
  • Rotate all secrets, API keys, and credentials from a different, uncompromised computer
  • Remove the @finantix/webcomponents package from all affected systems
  • Perform a full security audit and malware scan of affected systems
  • Review access logs and audit trails for any unauthorized activity
  • Consider full system reimaging if the package was installed on production or sensitive systems

Sources

  1. GitHub Advisory GHSA-hf7q-222g-654m · GitHub Advisory Database

Cite this entry

"Malware in @finantix/webcomponents." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 29, 2026; last updated June 29, 2026. https://supplychainattack.org/incident/malware-in-finantix-webcomponents-0dw40y

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 github-policy-bot (npm)

    The npm package github-policy-bot contained malicious code that exfiltrated host identifiers and environment metadata during installation via a postinstall script. The package name shadowed a legitimate Google-owned repository and was authored under a placeholder account claiming security research purposes.

    npmCompromised packageTyposquatting
  2. containedcritical

    Malicious code in crypto-javas (npm)

    The npm package crypto-javas contains malicious code in its postinstall hook and main entrypoint that harvests environment variables (including CI secrets like AWS_*, GITHUB_TOKEN, NPM_TOKEN) and exfiltrates them to an attacker-controlled backend. The package is presented deceptively as @wizlabs/js-crypto with a placeholder repository.

    npmCompromised packageTyposquatting
  3. containedcritical

    Malicious code in flydev (npm)

    The npm package flydev contains malicious code designed to destroy Windows systems. The package masquerades as a utility but executes destructive operations including filesystem deletion, process termination, memory exhaustion, and fork bombs when invoked.

    npmCompromised package
  4. containedcritical

    Malicious code in npm-wold (npm)

    npm-wold@1.1.1 contains malicious code in its postinstall script that fetches remote JSON from a hardcoded endpoint and dynamically invokes attacker-controlled functions with attacker-supplied arguments, enabling code execution at install time.

    npmCompromised package