backoffice-charges-module

On every `npm install`, the `preinstall` lifecycle script (`node index.js > /dev/null 2>&1`) silently HTTPS-POSTs a JSON payload to `https://avamnrwqo7.rbmock.dev/` containing the package name, a generated execution_id, `process.version`, `process.platform`, `process.arch`, and an ISO timestamp. Output is redirected to /dev/null to hide the network call from the installer. The package has empty description, author 'poc', declares a `main.js` that is not shipped, and uses an artificially high version number (1.999.0) — classic dependency-confusion/typosquat reconnaissance signals. The beacon allows whoever controls `avamnrwqo7.rbmock.dev` to enumerate which internal CI runners and developer hosts have resolved this name from the public registry instead of an internal one, identifying targets for follow-up payloads. ## Source: ghsa-malware (905a09d4d5d865bef6e4e577da4471244d53004ae5f02ef9bee2d9600f5d1756) 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.