Secure your code pre-launch and block attacks in real-time. Safeguard both user assets and your reputation.
Find and fix critical issues in your smart contracts before you launch.
Make sure your business logic is sound and free of flaws.
Always monitor mempool and on-chain transactions for suspicious activities.
Receive instant alerts on new threats such as oracle manipulation and flash loan attacks.
Block confirmed exploits in real-time to prevent them from draining funds.
Start on-chain responses, such as pausing contracts, to neutralize active threats.
Understand complex attack vectors to gain actionable intelligence. Help you proactively harden your protocol against emerging threats.
Secure Your Protocol Across Its Entire Lifecycle
“Partnering with BlockSec has been crucial to Tokenlon's mission of preserving the openness of DeFi while leveraging technology to create a safer, more trustworthy space for all. BlockSec's cutting-edge on-chain analytics allow us to identify high-risk addresses across multiple blockchains and navigate complex global regulations with confidence. Their expertise helps us safeguard our liquidity partners and consistently deliver a seamless, reliable DeFi experience for genuine users.”

Top 10 "Awesome" Security Incidents in 2025
To help the community learn from what happened, BlockSec selected ten incidents that stood out most this year. These cases were chosen not only for the scale of loss, but also for the distinct techniques involved, the unexpected twists in execution, and the new or underexplored attack surfaces they revealed.

#10 Panoptic Incident: XOR Linearity Breaks the Position Fingerprint Scheme
On August 29, 2025, Panoptic disclosed a Cantina bounty finding and confirmed that, with support from Cantina and Seal911, it executed a rescue operation on August 25 to secure roughly $400K in funds. The issue stemmed from a flaw in Panoptic’s position fingerprint calculation algorithm, which could have enabled incorrect position identification and downstream fund risk.

#9 1inch Incident: From Calldata Corruption to Forged Settlement: Binary Exploitation Goes On-Chain
On March 5, 2025, a third-party resolver integrated with 1inch Fusion V1 was exploited for over $5M after an unsafe calldata reconstruction in the settlement flow allowed attacker-controlled interaction lengths to trigger a pointer underflow and inject forged settlement data. The impact was amplified by a broken trust boundary, where resolver contracts treated forwarded calldata as authoritative based only on msg.sender, letting attacker-crafted payloads inherit settlement-level privileges while still passing access control.
For 500+ clients, from Web3 leaders to global regulators