@pcb-dp/qa-commons

@pcb-dp/qa-commons 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://webhook.site/d730a68c-27bd-4bb5-b1b9-d57a0a4b17ac/semz` in 1.0.0 and to `https://130.162.231.177:8443/` in 1.0.10. 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 (7d62530861df89932996e3e8aff140b44a2a40e2fbbf20cbb102b88bd3dfa2fc)
On npm install, @pcb-dp/qa-commons@1.0.0 runs a postinstall hook (`node./index.cjs`) that collects installer-side identifiers — os.hostname(), os.homedir(), process.platform, and CI-provider environment probes — and POSTs the JSON payload to a hardcoded third-party collector at https://webhook.site/d730a68c-27bd-4bb5-b1b9-d57a0a4b17ac/semz. The destination is an anonymous request-capture service unrelated to the package's stated purpose, and the beacon fires automatically on install with no caller configuration and no opt-out. This is reconnaissance-grade exfiltration of installer and CI-runner identity to an attacker-controlled endpoint.

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