Perimeter (@perimeter_sec) header
Perimeter (@perimeter_sec) profile picture

Industry leading security services specialized in fuzzing, securing DeFi's largest protocols

Joined January 2024
Photo by Perimeter (@perimeter_sec)Photo by Perimeter (@perimeter_sec)Photo by Perimeter (@perimeter_sec)Photo by Perimeter (@perimeter_sec)Photo by Perimeter (@perimeter_sec)Photo by Perimeter (@perimeter_sec)Photo by Perimeter (@perimeter_sec)Photo by Perimeter (@perimeter_sec)Photo by Perimeter (@perimeter_sec)Photo by Perimeter (@perimeter_sec)
Three fuzzing engagements with @monad. Monocle: e2e fuzzing by replaying mainnet & testnet against invariants tx-fuzz: RPC and execution client fuzzed under load Native C++ fuzzers: execution client and compiler fuzzed directly, checked against evmone Big credit to @monad.
3
1
2
20
1,274
Perimeter retweeted
Awesome resource for EVM Fuzzing, every Solidity developer should study this, do not skip your fuzz testing Tens of tools and solutions, Fizz from pashov/skills also mentioned🙏Thank you for compiling this list and the contribution @rappie_eth 🫡 github.com/perimetersec/evm-…
6
29
216
9,818
Shout out to @rappie_eth with @perimeter_sec for finding the above example. He's been fuzzing behavior differences in various solidity compilers. 3/3
1
2
21
1,375
Perimeter retweeted
Found this through differential fuzzing and first thought it was critical. Turns out --via-ir can change a function's behavior, as documented among the breaking changes (link below). Sharing this because it surprised me, and will probably surprise others as well.
Most people don't know that the --via-ir flag makes changes in the Solidity language. If using it to compile with, your code can do different things from compiling without it. If using it, here's some things you should do: 1/3
1
4
25
1,789
We are donating $100 to each of these public goods on @Giveth QF Round 16. Most of them are tools we actually use in our fuzzing work. The rest are important for the ecosystem we operate in. All open source, zero revenue. Going one by one 👇
7
6
3
25
2,168
SEAL 911. Hopefully you never need them but if you do, they are there 24/7, doing the invisible work saving millions. qf.giveth.io/project/seal-91…
1
1
185
The round has less than 4 days left. If these matter to you, contributions have outsized impact. Appreciate the teams behind all of them!
3
146
🛡️ $69 Million TVL Saved Our very own @gbrigandi reported a critical vulnerability, saving $69,000,000 in TVL for @Polkadot. We’re proud to strengthen the ecosystem through responsible disclosure and proactive security research. Blog post coming soon! PS: Found with fuzzing
6
2
7
47
17,995
Built the tools. Found the bugs. We’re excited to welcome Gianluca Brigandi (@gbrigandi) to Perimeter as Tooling Specialist. • Author of Traverse, Tameshi, and ThalIR • Multiple confirmed bounties
2
2
2
12
1,508
No generic workflow. Codebase-specific tooling. His approach: • Custom tooling for each codebase • Combine static analysis, fuzzing, compiler methods + more • Fine-tuned to target the system Result: • Deep, novel bugs • Confirmed bounties
1
4
188
More to come. One particularly compelling piece of Gianluca’s work will be public soon.
4
177