jsb-adapternpm

package.json declares a dependency whose key (jsb-adapter) equals this package's own name and whose value is the bare HTTPS URL https://repo.securityctrl.com/jsb-adapter instead of a registry version range. On npm install, npm fetches whatever tarball that host currently returns, unpinned and with no integrity check, and runs any lifecycle scripts inside it — so the code executed on the installer is whoever controls repo.securityctrl.com at install time, not the published tarball. The shipped index.js is an inert stub, so the manifest line is the entire published payload. Aggravating shape: the dependency key matches the package's own name and the version 45.0.0 is implausibly high, consistent with dependency-confusion targeting an internal package of the same name.

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.