ton-vulnerability-scanner

To audit TON FunC contracts, scan the source files to identify critical vulnerability patterns including integer-as-boolean misuse, fake Jetton contracts, and unsafe gas-forwarding logic. The process generates a structured report with file references and remediation suggestions.

When reviewing TON Jetton contracts, look for fake Jetton contract vulnerabilities alongside unsafe gas-forwarding logic. A targeted FunC audit detects these critical patterns and provides actionable remediation guidance.

Yes, you can analyze FunC source files (.fc/.func) to detect integer-as-boolean misuse. The scan enforces platform detection for FunC files and assesses pattern-based risks to produce a structured vulnerability report.

The best way to check gas-forwarding patterns is running a pre-launch audit of TON dApps using pattern-based risk assessment. This identifies unsafe gas-forwarding logic in FunC code and provides structured remediation suggestions.

No, the vulnerability scanner operates without external dependencies. It directly enforces platform detection on FunC files and evaluates them against known security patterns to output a comprehensive vulnerability report.

You need a specialized scanner because TON FunC contracts have platform-specific vulnerabilities like boolean handling and Jetton logic issues that generic tools miss. A specialized audit ensures accurate pattern-based risk assessment and targeted remediation.