ir-annuities-client-authentication-module

Details

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

## Source: amazon-inspector (0d813fc9c0831847a602c97803b7e53603edfb6acef4386e4cde2927c2a7a297)
package.json declares a dependency whose key equals the package's own name (`ir-annuities-client-authentication-module`) and whose value is a plain HTTPS URL to a non-registry host (`https://repo.securityctrl.com/ir-annuities-client-authentication-module`) instead of a semver range. On `npm install`, npm fetches whatever bytes that URL currently returns and installs them as this dependency, with no version pin, no integrity hash, and no registry provenance; any lifecycle scripts contained in the fetched artifact execute on the installer. The dependency key matching the package's own name creates a dependency-confusion shape that can win resolution against an internal package of the same name. The shipped index.js is an inert stub, so the manifest itself is the delivery mechanism — the absence of local scripts does not prevent the fetch or its lifecycle execution.

## Source: ghsa-malware (f38632ba56937eb99efe50ecefa5ca7a51b601c484b2e11c3a382cf4a33b9bf9)
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)

• 30.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.