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 (58c08ea2abb307f6ecb9a1896fcc3980e9a1eaf8b29044db67cd985654e1db16)
The package is a stub whose main module exports a Proxy that returns a no-op for every property access, providing none of the functionality implied by the package name or its 'compatibility shim' description. Its only real behavior is beacon.cjs, which collects host and install identifiers (hostname, install path, process.cwd(), process.version, package name/user-agent) and POSTs them to the hardcoded bare-IP HTTP endpoint http://185.158.107.175:8787/_ah/dc. The beacon fires both automatically at install time via scripts.postinstall and again when the module is loaded via require(), because index.js invokes beacon.fire(). The shape — stub module, hardcoded non-DNS bare-IP C2 over plain HTTP, collection of installer host identifiers at install and require time — is consistent with a dependency-confusion / internal-name-squat reconnaissance beacon reporting successful installation inside private build environments.