ubiquiti-agents-link-mcpnpm
ubiquiti-agents-link-mcp is a confirmed malicious npm package (MAL-2026-16409) that executes malicious code on install (malicious versions 0.0.1, 0.0.2, 0.2.0…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in ubiquiti-agents-link-mcp (npm)
What this malware does
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ubiquiti-agents-link-mcp (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ubiquiti-agents-link-mcp across your stack and pipelines.
If you installed it — respond
Remove ubiquiti-agents-link-mcp from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If ubiquiti-agents-link-mcp was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks ubiquiti-agents-link-mcp before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks ubiquiti-agents-link-mcp-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.