@riskine-frontend/design-elementsnpm
@riskine-frontend/design-elements is a confirmed malicious npm package (MAL-2026-4425) that executes malicious code on install (malicious version 99.9.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @riskine-frontend/design-elements (npm)
What this malware does
@riskine-frontend/[email protected] is a near-empty package whose only effect on install is to pull an external dependency. index.js contains just module.exports = {}, package.json has placeholder metadata (empty description, empty author, no repository), and the version is inflated to 99.9.1 — the canonical shape of a dependency-confusion squat designed to win npm version resolution against an internal package of the same scoped name. Its single dependency ltidisafe is resolved not from the npm registry but from an arbitrary tarball URL https://ltidi.storage.googleapis.com/depenconf/ltidisafe-2.4.2.tgz — note the literal depenconf/ (dependency confusion) folder name. Installing this package causes npm to fetch and install that external GCS-hosted tarball, executing any lifecycle scripts it declares on the installer's machine. The combination of inflated version + empty wrapper + external non-registry tarball + depenconf path is unambiguous attacker tradecraft against Riskine's internal build systems.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @riskine-frontend/design-elements (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @riskine-frontend/design-elements across your stack and pipelines.
If you installed it — respond
Remove @riskine-frontend/design-elements from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @riskine-frontend/design-elements 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 @riskine-frontend/design-elements 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 @riskine-frontend/design-elements-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.