←
Synack Red Team2,826 posts
Synack Red Team avatar

Synack Red Team

@SynackRedTeam

The power behind the @Synack platform is an elite team of the world's top cybersecurity researchers. Our best are honored at acropolis.synack.com

◷ Joined May 2014▧ 422 Photos and videos
Synack Red Team avatar
Synack Red Team@SynackRedTeam·Nov 9

Hello, Thailand 😎 We're kicking off our annual HackerHangout this week! Big thanks to the partners, family, and friends who support us all year and make the SRT community possible.

Post attachment
Synack Red Team avatar
Synack Red Team@SynackRedTeam·Oct 28

A random-looking GUID was the only thing protecting guest PII on a food ordering platform. Maybe it wasn’t so random? Synack Red Team researcher Mustafa Öztaş (rickiex) spotted the pattern. A forgotten endpoint did the rest. CVSS 8.7. synack.com/exploits-explaine…

Post attachment
VMblog avatar
⟳ Synack Red Team retweeted
VMblog@vmblog·Oct 23

On October 21, government websites across Europe went dark. Dutch, French, Danish, and Finnish agencies took public-facing services offline after critical vulnerabilities surfaced in #PHP, the programming language behind approximately 75% of websites. The flaws had been sitting in the codebase for years until AI tools uncovered them. Although a fix has been shared publicly, #AI has made it easy for attackers to reverse engineer what changed. Amazon reported that its security team saw an exploitation attempt against a honeypot system on October 17, four days before the disclosure. Defenders were behind even before the advisory went out. In this post, Mark Kuhr and Nabil Hannan answers the broader questions #security teams are asking about how this story illustrates the new normal in offensive security. vmblog.com/bylines/5-questio… #cybersecurity #phpflaw

Synack Red Team avatar
Synack Red Team@SynackRedTeam·Oct 9

A dangling CNAME looked like a low-impact finding until Synack Red Team member Plamen Dimitrov (d7x) found a custom JavaScript field in the third-party portal behind it. One line of code gave him cookie control across every subdomain. hubs.ly/Q04zHfrF0

Post attachment
Synack Red Team avatar
Synack Red Team@SynackRedTeam·Oct 1

“If you don’t enjoy it, you’re not going to push through those hard times.” SRT researcher AnInsiderThreat drops some real talk on passion, persistence, and avoiding burnout in bug bounty:

0:48
Synack Red Team avatar
Synack Red Team@SynackRedTeam·Sep 29

What do you do when the device you're attacking refuses to talk back? Synack Red Team researcher Shea Norwood found an unauthenticated command injection bug in a Nortek Linear eMerge E3, the appliance behind badge readers, door locks, and the credential database for facilities. The endpoint would run any command handed to it. It just never said so. No error, no output, no visible change. So Shea made it talk in a language it couldn't help but speak. A sleep 5 payload delayed the response by five seconds. Double the sleep, double the delay. Then came the real test: smuggling command output out as a DNS lookup, caught on a Burp Collaborator listener the appliance never knew existed. The HTTP response gave up nothing. The DNS traffic gave up everything, including the exact user the shell was running as. Full compromise of a door controller isn't just a shell. It's physical access, employee records, and compliance exposure riding on one unsanitized parameter. Blind doesn't mean unexploitable. Read how timing and DNS turned a silent endpoint into full remote code execution 👇 hubs.ly/Q04yBNbz0

Post attachment
Synack Red Team avatar
Synack Red Team@SynackRedTeam·Sep 18

“I had three SQLis I submitted two days ago; they got triaged yesterday." ⚡️ - SRT researcher Austin on the advantages of hacking with @synack compared to other platforms. Interested in joining the Synack Red Team? Visit our website to learn more: synack.com/red-team

0:34
Malcolm Stagg avatar
⟳ Synack Red Team retweeted
Malcolm Stagg@malcolmst·Sep 10

Thanks @SynackRedTeam and The Datatech Times! Glad to be able to share some more about this research.

Nice writeup from The Datatech Times on @malcolmst and his NatJack research. Stagg first discovered that NAT table entries could be corrupted or replaced while on assignment for the Synack Red Team. In his own words: “For a lot of business and enterprise customers, I would say the TCP and HTTP session hijacking techniques are the most dangerous, since a lot of internal network traffic is still unencrypted, and untrusted/trusted workloads often share the same NAT." Worth the read if you want the story behind the NatJack research: hubs.ly/Q04x8SM70

Synack Red Team avatar
Synack Red Team@SynackRedTeam·Sep 10

Nice writeup from The Datatech Times on @malcolmst and his NatJack research. Stagg first discovered that NAT table entries could be corrupted or replaced while on assignment for the Synack Red Team. In his own words: “For a lot of business and enterprise customers, I would say the TCP and HTTP session hijacking techniques are the most dangerous, since a lot of internal network traffic is still unencrypted, and untrusted/trusted workloads often share the same NAT." Worth the read if you want the story behind the NatJack research: hubs.ly/Q04x8SM70