Security audit

Megaeth Developer

Security checks across malware telemetry and agentic risk

Overview

This is a MegaETH developer guide with real blockchain transaction examples, but it does not install code, run commands, or hide data access.

Install only if you intend to build on MegaETH. Before running any command or code that sends, swaps, approves, bridges, or deploys, verify the chain ID, recipient, token, amount, spender, slippage, bridge address, and gas settings; prefer testnet or small-value trials first, and avoid unlimited approvals unless you fully trust the spender.

SkillSpector

By NVIDIA

Vulnerability Patterns

Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (7)

Vague Triggers

Medium

Confidence: 84% confidence
Finding: The skill's invocation scope is very broad and covers common wallet, transaction, swap, bridging, and contract-development tasks without clear boundaries or exclusion criteria. In an agent environment, this can cause over-invocation of a high-authority skill for sensitive financial operations, increasing the chance of unsafe guidance being applied where a narrower, more specialized workflow should be used.

Missing User Warnings

Medium

Confidence: 94% confidence
Finding: The file includes ready-to-run commands that send value and broadcast deployments against a live RPC endpoint without any adjacent warning that these actions are irreversible and may spend real funds. In a developer skill focused on wallet operations and deployment, users may copy-paste these examples directly, increasing the likelihood of accidental asset loss or unintended mainnet transactions.

Missing User Warnings

Medium

Confidence: 88% confidence
Finding: The examples show how to submit a signed transaction directly to the MegaETH mainnet RPC, but they do not include any warning that broadcasting a signed transaction is irreversible and can transfer real funds. In a developer-facing skill focused on wallet and transaction operations, readers may copy-paste these commands into production contexts, increasing the chance of accidental mainnet submission and unintended asset loss.

Missing User Warnings

Low

Confidence: 89% confidence
Finding: The guide recommends using third-party RPC providers and contacting the MegaETH team with transaction hashes, error messages, and reproduction steps, but it does not warn that these artifacts can contain sensitive operational metadata. In a blockchain development context, debugging bundles, HAR files, calldata, addresses, API-backed endpoints, and reproduction details may reveal private infrastructure usage, wallet relationships, internal app behavior, or undisclosed contract interactions.

Missing User Warnings

Medium

Confidence: 93% confidence
Finding: The CLI example uses `--yes` to suppress user confirmation while sending real assets, which removes a key safeguard against accidental or misdirected transfers. In a wallet-operations skill, copy-pasteable examples are likely to be used directly, so presenting a non-interactive transfer flow without an adjacent warning materially increases the risk of irreversible fund loss.

Missing User Warnings

Medium

Confidence: 94% confidence
Finding: The ERC20 transfer CLI example also suppresses confirmation with `--yes`, enabling immediate token transfer without a final human check. Because token transfers on MegaETH are fast and irreversible, this is especially risky in documentation intended for direct operational use.

Missing User Warnings

High

Confidence: 97% confidence
Finding: The approval example uses `maxUint256`, granting effectively unlimited token spending to the specified spender. If the spender is malicious, compromised, or incorrectly specified, the wallet's entire token balance can be drained without further approval, making this substantially more dangerous than a single transfer.

VirusTotal

61/61 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.