Malware in @dsft/ft-element
Malware discovered in the npm package @dsft/ft-element. Systems with this package installed are considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- @dsft/ft-element
A critical malware incident was identified in the npm package @dsft/ft-element. According to the GitHub Advisory (GHSA-5g88-35hm-8xr7), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory indicates that the malicious package grants full control of affected systems to an outside entity. All secrets and keys stored on compromised computers should be rotated immediately from a different, unaffected system.\n\nWhile 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.
Indicators of compromise
- Packages
- @dsft/ft-element
Remediation
- Immediately remove the @dsft/ft-element package from all systems
- Rotate all secrets, keys, and credentials from a different, unaffected computer
- Assume full system compromise and conduct forensic analysis
- Review system logs for unauthorized access or modifications
- Consider rebuilding affected systems from clean media if possible
- Audit all systems that may have had access to secrets or keys from compromised machines
Sources
- GitHub Advisory GHSA-5g88-35hm-8xr7 · GitHub Advisory Database
Cite this entry
"Malware in @dsft/ft-element." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 14, 2026; last updated July 15, 2026. https://supplychainattack.org/incident/malware-in-dsft-ft-element-1lrq9m
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malicious code in @telekom-ods/react-ui-kit (npm)
@telekom-ods/react-ui-kit version 2.6.9 on npm contained malicious code in an install hook that exfiltrated system information (/etc/passwd, /etc/hosts, /etc/shadow, id output) via HTTP POST to an OAST callback server. The compromised package was published under the legitimate telekom-ods publisher account, suggesting either account takeover or supply-chain injection.
npmCompromised packageAccount takeover - resolvedcritical
Malicious code in mcp-util-helpers (npm)
The npm package mcp-util-helpers contained malicious code in its preinstall hook that performed host reconnaissance and established a remote code execution channel via a hardcoded webhook.site endpoint. The script exfiltrated system information, credentials, and environment variables, and could execute arbitrary commands or download and run remote binaries on installation.
npmCompromised packageMalicious commit - containedcritical
Malicious code in boring-vault (npm)
boring-vault is a malicious npm package impersonating the BoringVault smart-contract framework. It executes install-time payloads that harvest environment variables, credential files, and SSH/cloud configuration data, exfiltrating them to an attacker-controlled webhook.
npmTyposquattingCompromised package - containedcritical
Malicious code in @years17/n8n-nodes-utils-helper (npm)
The npm package @years17/n8n-nodes-utils-helper contained malicious code that performs host reconnaissance, harvests secrets, and exfiltrates data to an external server. The attack executes automatically on package installation and when the module is required, and also provides an operator-triggered reconnaissance primitive via a bundled n8n node.
npmCompromised package