ton-vulnerability-scanner

To scan TON FunC contracts for vulnerabilities, run the scanner against your codebase to surface vulnerable patterns like integer-as-boolean misuse, fake Jetton transfer notifications, and forward TON without gas checks. It provides mitigation steps and testing strategies to improve your dApp's security posture.

TON Jetton transfer flows carry security risks like fake transfer notifications, integer-as-boolean misuse, and forwarding TON without gas checks. Scanning for these vulnerability patterns helps identify potential token loss vectors and provides mitigation guidance for contract audits.

Forwarding TON without gas checks creates a vulnerability pattern where insufficient gas causes transaction failures. The scanner detects this issue in FunC contracts and provides mitigation steps and reference patterns to implement proper gas validation logic.

Yes, the scanner is designed for security audits of TON dApps, Jetton interactions, and gas-forward flows. It satisfies detection of three key vulnerability patterns with targeted mitigation guidance and testing strategies suitable for comprehensive reviews.

Fixing fake Jetton transfer notification vulnerabilities requires implementing proper sender validation in your FunC contract. The scanner detects this pattern and provides mitigation steps, testing strategies, and reference patterns to prevent unauthorized transfer notifications.

Automated TON vulnerability scanning is limited to three specific patterns: integer-as-boolean misuse, fake Jetton transfer notifications, and forward TON without gas checks. It provides mitigation guidance but should be part of a broader manual security review for comprehensive coverage.