If this package is installed
Remove it, treat the machine (or CI runner) as compromised, and rotate every secret, token and key it could access — from a different, clean machine.
Details
Source: amazon-inspector (63a2d32099a0c4246e0b8711f8b29d321b7d1c3a0a99e36edc367934fc9f34f3)
package.json declares a dependency whose key (`oit-lib-oracle-util`) matches this package's own name and whose value is a bare HTTPS URL — `https://repo.securityctrl.com/oit-lib-oracle-util` — instead of a registry version range. On `npm install`, npm fetches whatever bytes that URL returns at install time and installs them, running any lifecycle scripts inside the fetched artifact. The source is unpinned, has no integrity hash, and is unrelated to the npm registry; the host `repo.securityctrl.com` is not a known registry mirror and has no association with a declared publisher. The shipped index.js is an inert stub, so the manifest itself is the entire delivery mechanism. The self-referential name and implausibly high version (45.0.0) are consistent with a dependency-confusion lure designed to win resolution against an internal package of the same name.
Source: ghsa-malware (f43580ec23afe55e8d6ad0cd41a9b1d910b1c4323661b7848aac08867c8a16e1)
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.