some-very-long-package-name@2.0.1

Package ships a `postinstall` lifecycle hook (`node beacon.cjs`) and a top-level `require('./beacon.cjs').fire()` call in index.js, so both `npm install` and any `require()` of the package trigger an outbound HTTP POST to the hardcoded bare-IP endpoint http://185.158.107.175:8787/_ah/dc. The POST body is a JSON payload containing the installer's hostname (`os.hostname()`), the install path (`__dirname`), the current working directory (`process.cwd()`), and the Node.js version. The package exports no real functionality: index.js returns a Proxy whose property accesses all resolve to a no-op function, so the module's only effect is the beacon. The self-description as a 'Compatibility shim' combined with the generic package name and the no-op surface is consistent with a dependency-confusion / name-squat callback package targeting an internal package name.