Malware in accounts-loading-state
The npm package accounts-loading-state was found to contain malware, potentially giving full control of affected systems to an outside entity. All systems with this package installed should be considered fully compromised.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- accounts-loading-state
The npm package accounts-loading-state was identified as containing malware. According to the GitHub Advisory (GHSA-9pwq-f6rq-8q69), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends that all secrets and keys stored on affected computers be rotated immediately 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 compromise.\n\nThis represents a critical supply chain attack through a compromised npm package with potential for complete system takeover.
Indicators of compromise
- Packages
- accounts-loading-state
Remediation
- Immediately isolate any system with accounts-loading-state installed from the network
- Rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the accounts-loading-state package from all systems
- Perform a full security audit and malware scan on affected systems
- Review system logs and access logs for signs of unauthorized activity during the period the package was installed
- Consider full system reimaging if complete compromise is suspected
Sources
- GitHub Advisory GHSA-9pwq-f6rq-8q69 · GitHub Advisory Database
Cite this entry
"Malware in accounts-loading-state." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 3, 2026; last updated August 3, 2026. https://supplychainattack.org/incident/malware-in-accounts-loading-state-1li5r1
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in sme-rko-finance-front-operations-special-payments (npm)
The npm package sme-rko-finance-front-operations-special-payments contained malicious code that downloads and executes platform-specific binaries from attacker-controlled infrastructure upon require(). The package employed obfuscation techniques to evade static analysis and included dual dropper paths in both index.js and lib/telemetry.js.
npmCompromised package - activecritical
Malware in bnpl-blocks-desktop-bnpl-anchor-title
Malware discovered in the npm package bnpl-blocks-desktop-bnpl-anchor-title. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package - containedcritical
Malicious code in sme-rko-finance-front-operations-notifications-models (npm)
The npm package sme-rko-finance-front-operations-notifications-models contained malicious code that acts as a native-binary dropper, downloading and executing platform-specific binaries from attacker-controlled Cloudflare Workers domains and DNS fallback servers upon package require.
npmCompromised package - resolvedcritical
Malicious code in sme-rko-finance-front-operations-penalty (npm)
The npm package sme-rko-finance-front-operations-penalty contained malicious code that downloads and executes platform-specific binaries on require(). The dropper uses obfuscated string concatenation and DNS fallback channels to retrieve payloads from attacker-controlled infrastructure.
npmCompromised package