ubiquiti-agents-link-mcpnpm

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.

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.

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.