sc-font-iconsnpm
sc-font-icons is a confirmed malicious npm package (MAL-2026-12800) that opens a backdoor for remote access (malicious version 9999.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in sc-font-icons (npm)
What this malware does
The package's preinstall script runs automatically on npm install and collects installer-side identifiers — os.hostname(), os.userInfo().username, process.cwd(), the configured npm registry, and CI repository slugs from GITHUB_REPOSITORY / CI_PROJECT_PATH — and sends them over plain HTTP GET to a hardcoded bare-IP endpoint at http://75.119.137.232:31337/depconfuse as query parameters. The version number (9999.0.0) and the beacon path (/depconfuse) are consistent with a dependency-confusion probe: the artifact exists to be pulled into internal builds that mis-resolve a private package name to the public registry, and to report back the internal package name, host, user, working directory, private registry URL, and repository slug of any environment that installs it. The destination is a bare IP with no TLS, unrelated to any legitimate npm publishing infrastructure, and the collected fields disclose internal repository and infrastructure naming to a third party.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for sc-font-icons (version 9999.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sc-font-icons across your stack and pipelines.
If you installed it — respond
sc-font-icons establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If sc-font-icons was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks sc-font-icons before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks sc-font-icons-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.