npm-extension

Details

---
_-= Per source details. Do not edit below this line.=-_

## Source: amazon-inspector (2a6c4f2b94932e8bcb68c0a146d536b7e3a00d48041aa5a6fc9edf9f82ae5244)
package.json declares a dependency whose value is a bare HTTPS URL (https://repo.securityctrl.com/npm-extension) rather than a registry version range. On npm install, npm fetches whatever tarball that host returns and executes any lifecycle scripts inside it, unpinned and without integrity verification. The dependency key equals the package's own name, producing a dependency-confusion shape in which resolution is forced through the off-registry host. The shipped index.js is an inert stub, so the manifest line is the entire published payload — the fetched third-party code is what actually runs on installer machines.

## Source: ghsa-malware (4187b797ddf66bc09166a921578aabac2323e67c3059b573aa255310157838e3)
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.

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.