Ae1
- Category
- analysis-evasion
- Confidence
- 100% confidence
- Finding
Referenced artifact was not completely inspected
- Content
md command: node script/index.js
Security audit
Security checks for vulnerabilities and agentic risk
This skill performs a narrow Hymatrix bridge transaction lookup and does not show hidden, persistent, destructive, or credential-seeking behavior.
Install only if you are comfortable with transaction hashes you provide being sent to Hymatrix's bridge scan API. The skill appears narrow and non-persistent, but its trigger wording and outbound-data disclosure could be clearer.
Referenced artifact was not completely inspected
command: node script/index.js
The skill declares a command (node script/index.js) that likely performs network access, but the manifest does not specify any permissions or allowed-tools boundary. This creates an authorization ambiguity where an agent or runtime may execute network-capable code without an explicit least-privilege declaration, making review and containment harder.
The trigger says to use the skill when the user provides a transaction ID or hash and asks for 'the following information,' but it does not enumerate concrete trigger phrases, supported question types, or exclusion cases. This broad wording can cause unintended invocation for general transaction-related questions that mention a hash without clearly requesting a bridge-status lookup.
The natural-language instructions are written as mandatory Chinese guidance to the agent and do not indicate that the user may choose another language. This creates a locale/language policy concern because the skill appears to assume or enforce a specific language without opt-in or justification.
This code sends the user-provided transaction identifier to an external API endpoint, which is a network operation involving user data. There is no confirmation prompt, logging, comment explaining the disclosure, or other visible user warning in this file about the outbound request.
No suspicious patterns detected.