ssite-mock-server

ssite-mock-server is a dependency-confusion package with no functional code (its description is "Authorized Test Package"). Its postinstall script runs `node ./index.cjs` on npm install, which POSTs the hostname, home directory, platform and CI provider (GitHub Actions, GitLab CI, Azure Pipelines or Jenkins) to `https://130.162.231.177:8443/`. It was published by the npm account notsemz, which published two more packages with the same beacon on 2026-10-29 and seven placeholder-only names.

---
_-= Per source details. Do not edit below this line.=-_

Source: amazon-inspector (09dbc445d21cbcfe7afcda44cc8952e25a1444c0dbe56b9376ef132c5e513981)
On npm install, the package's postinstall hook executes index.cjs, which collects host reconnaissance data (os.hostname(), os.homedir(), process.platform) and CI-provider fingerprints derived from well-known CI environment variables, then POSTs them as JSON to a hardcoded bare-IP HTTPS endpoint at https://130.162.231.177:8443/. The destination is not a package publisher domain, is not caller-configurable, and the behavior fires automatically on default install with no documentation or opt-out. The package's self-description as a mock/test server does not match this install-time outbound beacon behavior.

Source: ghsa-malware (b78321d5059e11bc71690bbb965780622cd835221d353fecb34eb51ee2e9716e)
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.