bui-react-10themes

Details

**Severity:** Critical

**Affected versions:** `= 45.0.0`

## Source: amazon-inspector (0a333445d0f8345bc824161bcc7f6487a59ba9f1f7a852da2643eb7c27dd849b)
package.json declares a dependency whose key equals this package's own name (bui-react-10themes) and whose value is a bare HTTPS URL (https://repo.securityctrl.com/bui-react-10themes) rather than a registry version range. There is no version pin and no integrity hash. On npm install, npm fetches whatever tarball is served from repo.securityctrl.com and installs it, executing any lifecycle scripts it contains. The shipped in-tree code is an inert stub, so the manifest edge is the entire installed surface. The self-name pattern (dependency confusion shape) combined with the implausibly high 45.0.0 version is consistent with an attempt to win resolution against an internal package of the same name.

---

Credit: [OpenSSF](https://github.com/ossf/malicious-packages) ([source](https://github.com/ossf/malicious-packages/blob/d75ebb673b0185a99abe46e9e4a60aaa467fa7d8/osv/malicious/npm/bui-react-10themes/MAL-2026-15529.json))

**References:**
- https://github.com/ossf/malicious-packages/blob/d75ebb673b0185a99abe46e9e4a60aaa467fa7d8/osv/malicious/npm/bui-react-10themes/MAL-2026-15529.json
- https://www.npmjs.com/package/bui-react-10themes/v/45.0.0
- https://github.com/advisories/GHSA-jv92-xghh-84rr

Compromised versions (1)

• = 45.0.0

Any computer that installed or ran a compromised version should be considered fully compromised. Rotate every secret on that machine from a clean environment.