ubiquiti-agents-link-mcp@0.2.0

The package's bin entry (index.js) runs `execSync('id')` and collects `os.userInfo().username` and `os.hostname()`, then HTTPS-POSTs the JSON payload to the hardcoded Burp Collaborator subdomain `uhffaanwxy0io5bfc0icu5lpug07o9cy.oastify.com` at a randomized path. The package occupies an npm name referenced by a vendor UI that instructs operators to invoke it via `npx`, so running the documented command causes host identity data to leave the operator's machine to a third-party OAST endpoint with no opt-in. The tarball metadata self-describes the release as a placeholder registered to demonstrate the dependency-confusion vector, but the shipped code performs a real installer-side data leak on execution, and the namespace remains available for future publishes by the same account with operator-level code execution on any host following the vendor's instruction. ## Source: ossf-package-analysis (bb2bd11478a4b45a05adf8ac3c9b4ddeb169297b9c280916a25eccd4dd827922) The OpenSSF Package Analysis project identified 'ubiquiti-agents-link-mcp' @ 0.0.1 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity.