x86 formal verification is coming!
The (first?) published machine-checked proof of a security property for the end-to-end execution of a Linux process running an x86 binary statically linked against glibc.
And we believe it scales!
A joint research project with @zellic_io 🧵👇
Atul Agarwal retweeted
Huge thanks to @secfence for supporting Offensivecon again as Diversity Sponsor!
Happy to support the very best.
We’d be there at OffensiveCon, yet again!!
Many thanks to @secfence for their diversity sponsorship and help in empowering the community!
Atul Agarwal retweeted
Happy to sponsor @nullcon
We are hiring for multiple positions, DM us and we would love to meet you at #Nullcon2025
Atul Agarwal retweeted
Come see us at #BHMEA24 at the @DSCI_Connect India Pavilion - H1 T91
We are showcasing are Next-Gen Mobile Forensics Platform!
Atul Agarwal retweeted
We have a spare #37c3 pass. If anyone is interested, please feel free to DM!
#37c3 #ChaosCommunicationCongress
Atul Agarwal retweeted
😎We are excited to Welcome back our sustaining sponsor Secfence @secfence as 🎴Lanyard Sponsor
Stay updated here ➡️bit.ly/3VWR8g6
#NullconGoa2023 #Infosec #Conference
Always happy to support exceptional research & talent!
We will be there, let’s meet up :)
[Zer0Con2023] "Silver Sponsor"
Thanks to Secfence(@secfence) for sponsoring the "Silver"
Secfence is an Offensive Security company specialising in vulnerability research & turnkey platforms.
#Zer0Con2023
7
1,853
Atul Agarwal retweeted
We’ll be at @hexacon_fr, Paris. Come say Hi!
We’re hiring for full time/contractual positions.
Atul Agarwal retweeted
Popping shells @defcon. More than 20 vendors affected to an RCE in the network stack. Do you know what does your router is running? securityweek.com/realtek-sdk…
Atul Agarwal retweeted
Windows: Credential Guard Domain-joined Device Public Key EoP bugs.chromium.org/p/project-…
Atul Agarwal retweeted
The quantum state of Linux kernel garbage collection CVE-2021-0920 (Part I) googleprojectzero.blogspot.c…
Atul Agarwal retweeted
New blog post for HInvoke. It allows calling .NET runtime functions or accessing properties using only hashes as identifiers. Reducing obvious identifiers for analysts. Post also includes a little trick to avoid using PInvoke.
dr4k0nia.github.io/dotnet/co…


























