Malicious code in tabbables (npm)

__

Source: amazon-inspector (2fc629ecaf81d15034bbba33363e63776d106e6f58932e889baa4cb748b689eb)

package.json at line 11 declares a dependency whose key equals the package's own name (tabbables) and whose value is the raw HTTPS URL https://repo.securityctrl.com/tabbables rather than a registry version range. On npm install, npm fetches whatever tarball that URL currently serves and installs it, executing any lifecycle scripts it contains, with no version pin, no integrity/hash check, and no registry provenance. The shipped index.js is an inert stub, so the manifest URL is the sole payload-delivery mechanism; the tarball's behavior can be changed at any time by whoever controls repo.securityctrl.com. The self-referential dependency key also produces a dependency-confusion shape (an implausibly high 45.0.0 version competing with any internal package of the same name).

Source: ghsa-malware (580578f2de6ca207ca37218f58ff798855d032cbd2d824c6a6159ad194bc7303)

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.