@riskine-frontend/design-elements

@riskine-frontend/design-elements@99.9.1 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. ## Source: ghsa-malware (68bc93efbdd5282da5f3901689d5294249f5ec982f3592cba1092489e3e410c8) 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.