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 (417229f0823e3d64337cb454c2a3d7b8644bfd0eb4f676875f82eba80838f97f)
beacon.cjs defines BEACON = "http://13.140.137.222:8787/_ah/dc" and a fire() function that POSTs a JSON payload containing os.hostname(), __dirname (install path), process.cwd(), the Node.js version, and the package name to that hardcoded bare IP over cleartext HTTP. The package wires this to fire automatically on default install: package.json scripts.postinstall runs "node beacon.cjs", and index.js calls require('./beacon.cjs').fire() at top level, so a consumer require() also triggers the beacon. The destination is not caller-configurable and is not disclosed. The package self-describes as a "Compatibility shim" and exports an inert Proxy with no functional surface, so the beacon is the package's only effect. The combination of a hollow stub main, a hardcoded bare-IP plain-HTTP destination, and dual install+import execution matches a dependency-confusion / install-beacon reconnaissance package used to confirm execution inside internal build environments.
Source: ghsa-malware (a92510a22366de728e3ff108fed3d501566c544d1e74eaf4fa04c608f43bd601)
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.