ton-vulnerability-scanner

To audit FunC smart contracts on TON, use a scanner to analyze contract code for platform-specific vulnerabilities like integer-as-boolean misuse, fake Jetton implementations, and improper TON forwarding. It scans your project directory and provides actionable mitigation recommendations for identified flaws.

Common TON Jetton vulnerabilities include fake contract implementations, improper TON forwarding without gas checks, and integer-as-boolean misuse. Attackers can exploit these flaws in handlers like transfer_notification to potentially mint tokens out of thin air or drain contract funds.

Yes, you can scan Tact smart contracts alongside FunC code for TON network vulnerabilities. The scanner analyzes both languages to identify platform-specific patterns, checks project structure, and detects critical issues like fake Jetton contracts and improper forward TON handling.

To check for fake Jetton vulnerabilities in your TON contract, scan the code to identify whether the contract properly validates Jetton implementations. The scanner analyzes your transfer_notification handler and project structure to detect patterns that could allow attackers to mint tokens illegitimately.

Forwarding TON without gas checks in FunC contracts creates a critical vulnerability where transactions may fail or consume excessive fees. The scanner identifies improper TON forwarding patterns in your code and provides actionable recommendations to ensure gas validation before execution.

Run a vulnerability scan on TON smart contracts before deploying any new Jetton token or contract to mainnet. Use it during development to audit transfer_notification handlers and verify that integer-as-boolean misuse, fake Jetton patterns, and gas check issues are resolved pre-deployment.