T08 · Insecure Dependencies
- Location
SKILL.md:167- Finding
Unpinned Third-Party Dependencies Create a Supply-Chain Risk
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is mostly aligned with agent trust workflows, but it needs Review because it links wallet identities, wraps wallet transactions with a third-party package, and sends reputation/threat data to an external service.
Review before installing in any wallet-bearing or production agent. Use a dedicated wallet or pseudonymous identity, pin and audit the npm packages before use, confirm what transaction and report data Maiat receives, and avoid enabling automatic blocking/reporting unless its privacy, failure, and appeal behavior match your risk tolerance.
SKILL.md:167Unpinned Third-Party Dependencies Create a Supply-Chain Risk
SKILL.md:171Third-Party Wrapper Intercepts Wallet Transactions and Performs External Reporting
SKILL.md:31Unnecessary External Registration and Persistent Wallet-Identity Linking
The skill instructs users to register an on-chain identity by submitting an ENS-style name and wallet address to an external service without a prominent privacy warning. Because the action creates persistent public linkage and external disclosure of identity data, users may unintentionally deanonymize agents or operators and expose long-lived attribution metadata.
This is a real external transmission point because the example sends ENS and wallet identity data to a remote API for registration. In the context of a trust/identity skill, such transmission is expected, but it remains security-relevant because it shares sensitive identifiers with a third party and may establish persistent public identity linkage.
Every agent needs a Maiat Passport — your on-chain identity.
curl -X POST https://app.maiat.io/api/v1/passport/register \
-H "Content-Type: application/json" \
-d '{"ensName": "my-agent", "walletAddress": "0xYourWallet", "type": "agent"}'
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl https://app.maiat.io/api/v1/passport/lookup?q=agent-name
The Guard section promotes automatic transaction blocking and threat reporting but does not prominently disclose that transaction intent, counterparties, and threat telemetry may be sent to an external service for evaluation. In a wallet-protection context this is sensitive operational data, and silent blocking/reporting can surprise users and affect financial operations or privacy.
The skill strongly encourages always reporting outcomes with a wallet identifier, but does not warn that this sends job/activity metadata tied to the reporter address to an external service. This can create a detailed behavioral trail linking agent activity, counterparties, and success/failure outcomes to a persistent identity.
The manifest describes the skill as trust infrastructure for registering agent identities, checking agent trust scores, and protecting transactions between agents. However, the file also exposes substantial token-analysis functionality, including honeypot detection, rug-pull prediction, liquidity analysis, and multi-source token forensics, which goes beyond verifying another agent before transacting.
The threat-reporting flow allows user-submitted reports to contribute to ecosystem-wide blocking after three reports, yet it does not clearly warn about the downstream consequences or external sharing of submitted intelligence. Without strong disclosure and safeguards, users may unknowingly participate in actions that affect third parties at network scale and expose sensitive investigative data.
This is a true external transmission because it sends threat intelligence about an address to a third-party API, and the resulting reports can influence blocking decisions across the ecosystem. The sensitivity is increased by the combination of external disclosure, possible reputational harm to third parties, and insufficient warning about network-wide effects.
Report malicious addresses to protect the entire network:
curl -X POST https://app.maiat.io/api/v1/threat/report \
-H "Content-Type: application/json" \
-d '{"maliciousAddress": "0x...", "threatType": "address_poisoning"}'
The manifest frames the skill around identity, trust-score lookup, and transaction protection, but the documented functionality also includes outcome reporting, review submission, scarab balance checks, threat reporting, and agent reputation services. These features materially expand the skill from a verifier/protector into a broader reputation and feedback network.
No suspicious patterns detected.