Back to skill

Security audit

tronlink-skills

Security checks for vulnerabilities and agentic risk

Overview

This TRON wallet skill is mostly read-only, but it installs and exposes a much broader persistent tool suite than the wallet-only skill describes, and it can leak configured API keys to non-TronGrid services.

Review carefully before installing. Prefer running the specific wallet commands locally from a reviewed copy instead of the one-command installer. Do not set TRONGRID_API_KEY or TRONSCAN_API_KEY unless the credential handling is fixed, and avoid global MCP or agent integrations unless you want all TRON suite tools available across sessions and projects.

Vulnerability Patterns
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
Findings (6)

T09 · Insecure Skill Coding Practices

Error
Location
scripts/tron_api.mjs:62
Finding

TronGrid API Key Disclosed to Unrelated Third-Party Services

Content
View full analysis
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Warning
Location
scripts/tron_api.mjs:71
Finding

TronScan API Key Embedded in Request URLs

Content
View full analysis
Remediation
View remediation

T03 · Remote Payload Retrieval and Execution

Error
Location
README.md:13
Finding

Mutable Remote Installation and Uninstallation Scripts Piped Directly into a Shell

Content
View full analysis
Remediation
View remediation
install.sh" | sha256sum -c - less install.sh sh install.sh ``` 4. Sign release artifacts with a documented signing key and require signature verification. 5. Avoid silent curl options for security-sensitive installation; failures should be visible. 6. Ensure the uninstaller is installed locally so users never need to retrieve mutable remote code to remove the product. ]]>

T03 · Remote Payload Retrieval and Execution

Error
Location
install.sh:66
Finding

Installer Activates Unpinned Remote Code as Persistent Agent and MCP Configuration

Content
View full analysis
/dev/null ok "Cloned to $INSTALL_DIR" fi ``` It then registers the downloaded executable globally and modifies Agent instruction state: ```sh # Method 1: Register as global MCP server (available in all projects) info "Registering MCP server (global)..." if claude mcp add -s user tronlink -- node "$INSTALL_DIR/scripts/mcp_server.mjs" 2>/dev/null; then ok "MCP server registered globally (25 TRON tools available in all projects)" fi ``` ```sh if [ ! -f "CLAUDE.md" ]; then cp "$INSTALL_DIR/CLAUDE.md" ./CLAUDE.md ok "Added CLAUDE.md to current project" else # Append if CLAUDE.md already exists if ! grep -qi "tronlink" CLAUDE.md 2>/dev/null; then echo "" >> CLAUDE.md cat "$INSTALL_DIR/CLAUDE.md" >> CLAUDE.md ok "Appended TronLink instructions to existing CLAUDE.md" fi fi ``` Codex integration is also installed across sessions: ```sh mkdir -p "$HOME/.agents/skills" ln -sf "$INSTALL_DIR/skills" "$HOME/.agents/skills/tronlink-skills" ``` ### Technical Analysis The installer does not pin a release tag or commit and does not verify a signature or expected digest. It subsequently activates that mutable content as a global MCP server, a persistent skill symlink, or project-level Agent instructions. These integrations are legitimate mechanisms for an Agent Skill, but global registration and automatic instruction-file modification exceed the minimum privilege necessa ...[truncated 1768 chars]
Remediation
View remediation

T08 · Insecure Dependencies

Warning
Location
README.md:34
Finding

Installation Documentation Executes an Unpinned Third-Party Package Through npx

Content
View full analysis
Remediation
View remediation
add TronLink/tronlink-skills ``` 2. Document the expected package publisher and integrity information. 3. Prefer a locally installed and lockfile-controlled dependency where feasible. 4. Use a trusted, versioned release of the installer rather than resolving the latest package dynamically. 5. Reassess the package and transitive dependencies before updating the pinned version. 6. Avoid recommending elevated execution for package-manager commands. ]]>

T03 · Remote Payload Retrieval and Execution

Error
Location
README.md:53
Finding

Agent Is Directed to Fetch and Follow Mutable Remote Instructions

Content
View full analysis
Remediation
View remediation
Vulnerability Patterns
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Tool MisuseTool Parameter Abuse, Chaining Abuse, Unsafe Defaults
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Findings (71)

Description-Behavior Mismatch

Critical
Category
Not specified by scanner
Confidence
99% confidence
Finding

The manifest explicitly says this skill must not be used for swap/trading and directs swap requests to a different skill, yet the server exposes a swap-quote tool. Even if it only returns quotes, it materially enables trading workflows and undermines policy-based tool separation, allowing an agent to bypass intended routing and user safety boundaries.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

Critical
Category
Not specified by scanner
Confidence
99% confidence
Finding

The manifest explicitly excludes staking and says to use tron-staking instead, but this server exposes staking list, staking info, and staking APY tools. This breaks capability isolation and lets an agent access staking operations through a skill that users and higher-level routing logic would reasonably trust as wallet-view-only.

Content

No source excerpt is available for this finding.

Chaining Abuse

High
Category
Tool Misuse
Confidence
98% confidence
Finding

The | sh shell-chaining pattern removes the user's opportunity to review downloaded content before execution and turns a remote fetch into immediate code execution. In the context of an AI-agent skill README, this is especially risky because users may copy-paste commands with elevated trust, increasing the chance of silent compromise.

Content

Scanner excerpt · README.md (reported line 16)May include surrounding context.

Recommended (auto-detects your AI environment)

bash
curl -sSL https://raw.githubusercontent.com/TronLink/tronlink-skills/main/install.sh | sh

This automatically detects Claude Code, Cursor, Codex, OpenCode, or Windsurf and configures everything.

Chaining Abuse

High
Category
Tool Misuse
Confidence
98% confidence
Finding

The uninstall flow also uses | sh, preserving the same arbitrary code execution risk while encouraging users to run it during cleanup without scrutiny. The skill context does not mitigate this risk; if anything, wallet-related branding may increase user trust and make unsafe execution more likely.

Content

Scanner excerpt · README.md (reported line 28)May include surrounding context.

sh uninstall.sh

Or run remotely:

curl -sSL https://raw.githubusercontent.com/TronLink/tronlink-skills/main/uninstall.sh | sh

text

Removes MCP registrations, symlinks, copied config files, and `~/.tronlink-skills`.

Tp4

High
Category
MCP Tool Poisoning
Confidence
98% confidence
Finding

The declared purpose is narrowly about a wallet-viewing skill for TRON balances, holdings, transaction history, and account info. The actual code does not implement wallet-checking behavior at all; it is an integration-guide shell/documentation file for installing and running the broader TronLink skills suite. It also references unrelated capabilities such as security audits, energy price checks, swaps, representative lists, and resource optimization. This is a materially different primary purpose from the declared wallet-information skill, so it should be flagged as a mismatch.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
99% confidence
Finding

The description presents a runtime skill for viewing TRON wallet balances, token holdings, and transaction history, with explicit exclusions for swapping and staking. The actual code chunk does not perform wallet/account queries at all. Instead, it is an installation/setup script for the entire TronLink skills package. It modifies the local environment, integrates with multiple AI tools, and advertises broader capabilities including swap and staking. This is a materially different primary purpose and includes undeclared system-modifying capabilities, so the description does not accurately represent the code.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
99% confidence
Finding

The declared description says this skill should help users inspect TRON wallet balances, token holdings, transaction history, and related account information. The supplied code does none of that. It does not connect to TRON, inspect wallets, read balances, query transaction history, or manage TronLink wallet state. Instead, its primary purpose is uninstalling the TronLink Skills package and related local integrations by deleting files and deregistering tooling. That is a materially different purpose and involves undeclared destructive local system actions, so this is a clear description-behavior mismatch.

Content

No source excerpt is available for this finding.

Ae1

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

Scanner excerpt · SKILL.md (reported line 37)May include surrounding context.

md
node scripts/tron_api.mjs wallet-balance --address <TRON_ADDRESS>

Ae1

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

Scanner excerpt · SKILL.md (reported line 45)May include surrounding context.

md
node scripts/tron_api.mjs wallet-balance --address <TRON_ADDRESS>

Ae1

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

Scanner excerpt · SKILL.md (reported line 62)May include surrounding context.

md
node scripts/tron_api.mjs wallet-balance --address <TRON_ADDRESS>

Ae1

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

Scanner excerpt · SKILL.md (reported line 70)May include surrounding context.

md
node scripts/tron_api.mjs wallet-balance --address <TRON_ADDRESS>

Ae1

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

Scanner excerpt · SKILL.md (reported line 78)May include surrounding context.

md
node scripts/tron_api.mjs wallet-balance --address <TRON_ADDRESS>

Ae1

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

Scanner excerpt · SKILL.md (reported line 86)May include surrounding context.

md
node scripts/tron_api.mjs wallet-balance --address <TRON_ADDRESS>

Description-Behavior Mismatch

High
Category
Not specified by scanner
Confidence
97% confidence
Finding

The guide exposes swap- and staking-related tools in the same integration surface even though the tron-wallet skill metadata explicitly says not to use this skill for swap/trading or staking. This scope mismatch can cause an agent to over-select this skill or assume authority beyond its declared purpose, increasing the chance of unintended tool use and policy bypass through ambiguous routing.

Content

No source excerpt is available for this finding.

Chaining Abuse

High
Category
Tool Misuse
Confidence
95% confidence
Finding

The explicit use of a pipe into sh chains remote retrieval directly into command execution, eliminating any review barrier and making compromise of the source or delivery path immediately actionable on the host. In an installer that also writes to home-directory agent/plugin locations and modifies project files, this pattern substantially increases the blast radius of a bad update.

Content

Scanner excerpt · install.sh (reported line 8)May include surrounding context.

sh
# TronLink Skills — One-Command Installer
#
# Usage:
#   curl -sSL https://raw.githubusercontent.com/TronLink/tronlink-skills/main/install.sh | sh
#
# Local development (no GitHub needed):
#   sh install.sh --local /path/to/tronlink-skills

Description-Behavior Mismatch

High
Category
Not specified by scanner
Confidence
98% confidence
Finding

The manifest for this skill limits scope to TRON wallet balance, holdings, and transaction history, explicitly excluding swap and staking. This installer registers '25 TRON tools' globally and elsewhere describes the package as 'Wallet · Market · Swap · Energy · Stake', indicating installation/integration of a much broader capability set than the wallet skill claims.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

High
Category
Not specified by scanner
Confidence
99% confidence
Finding

The manifest says this skill is for checking TRON wallet information and explicitly says not to use it for swap or staking. The installer banner presents the installed capability set as 'Wallet · Market · Swap · Energy · Stake', which materially exceeds the declared wallet-only scope.

Content

No source excerpt is available for this finding.

Known Vulnerable Dependency: axios==1.13.5 — 16 advisory(ies): CVE-2026-44494 (axios Vulnerable to Full Man-in-the-Middle via Prototype Pollution Gadget in `co); CVE-2026-44495 (axios Vulnerable to Credential Theft and Response Hijacking via Prototype Pollut); CVE-2025-62718 (Axios has a NO_PROXY Hostname Normalization Bypass that Leads to SSRF) +13 more

High
Category
Supply Chain
Confidence
97% confidence
Finding

The lockfile pins axios 1.13.5, which is flagged with multiple advisories including SSRF-related proxy handling and prototype-pollution/MITM-style issues. Even though this file is only a dependency manifest, the skill is a TRON wallet/account skill that will likely make outbound RPC/API requests to blockchain infrastructure, so flaws in the HTTP client are security-relevant and can affect request routing, credential handling, or response trust.

Content

No source excerpt is available for this finding.

Known Vulnerable Dependency: form-data==4.0.5 — 1 advisory(ies): CVE-2026-12143 (form-data: CRLF injection in form-data via unescaped multipart field names and f)

High
Category
Supply Chain
Confidence
87% confidence
Finding

form-data 4.0.5 is flagged for CRLF injection via unescaped multipart field names and filenames. This becomes exploitable when attacker-controlled values are inserted into multipart requests; while a wallet balance skill may not heavily rely on multipart uploads, the vulnerable package is still present transitively and could be abused if such request paths exist now or are added later.

Content

No source excerpt is available for this finding.

Known Vulnerable Dependency: ws==8.17.1 — 2 advisory(ies): CVE-2026-45736 (ws: Uninitialized memory disclosure); CVE-2026-48779 (ws: Memory exhaustion DoS from tiny fragments and data chunks)

High
Category
Supply Chain
Confidence
91% confidence
Finding

ws 8.17.1 is flagged for memory disclosure and memory-exhaustion denial of service issues. Wallet and blockchain tooling commonly use WebSocket connections for subscriptions or live account/transaction updates, so a vulnerable ws version can expose the process to remote instability or data leakage if it connects to malicious or compromised endpoints.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

High
Category
Not specified by scanner
Confidence
97% confidence
Finding

The manifested skill is scoped to wallet balance, holdings, and transaction history, but the MCP server exposes a much broader set of token analytics and market-intelligence tools. This violates least-privilege and creates a capability-expansion path where an agent selecting this wallet skill can perform unrelated market analysis actions the user and orchestrator did not intend.

Content

No source excerpt is available for this finding.

Intent-Code Divergence

High
Category
Not specified by scanner
Confidence
96% confidence
Finding

The module header advertises DEX swap and TRX staking support even though the manifest explicitly excludes those functions. This contradiction is dangerous because operators and automated tooling may trust the manifest while the implementation and documentation quietly encourage higher-risk capabilities.

Content

No source excerpt is available for this finding.

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · scripts/tron_api.mjs (reported line 738)May include surrounding context.

js
trx_24h_volume: trx.usd_24h_vol || 0,
      latest_block: sysData.database?.block || sysData.full?.block || 0,
      confirmed_block: sysData.database?.confirmedBlock || sysData.solidity?.block || 0,
      network_env: sysData.network?.env || "unknown",
    },
  }));
}

Description-Behavior Mismatch

High
Category
Not specified by scanner
Confidence
98% confidence
Finding

The skill manifest explicitly says this skill must not be used for swap/trading, yet the file exposes swap quote and routing commands and wires them into the CLI. This scope mismatch is dangerous because an orchestrator or downstream agent may invoke trading-related functionality through a wallet-inspection skill, bypassing intended policy separation and increasing the chance of unauthorized or misleading financial actions.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

High
Category
Not specified by scanner
Confidence
98% confidence
Finding

The manifest states staking belongs to another skill, but this file includes staking discovery and reward-related commands. Even if these commands are informational, embedding staking capabilities in the wrong skill undermines least-privilege and can cause an agent to use the wrong tool for sensitive financial workflows.

Content

No source excerpt is available for this finding.