I find the holes in your site before attackers do: leaked keys, open .env, admin doors, DNS hijack. Laravel/PHP, WordPress, Web3 frontends. 20 yrs in web.
@Josh_E_Wa 240 bug reports from 4k traders is basically a free pentest. The question I'd ask next: 245k trades for 4k people, how much of that is points farming through the API instead of real clicks? USDC prizes make scripts show up fast.
@payfrens The payment confirmation widget inside chat is the part I'd poke first. If it renders "paid" from what the client says instead of what landed onchain, a fren can fake a receipt. Does the server check the signature before the widget shows up?
@Henry_J_Brew "Claude on its own shipped an access bug" is the line. the nasty ones are rarely in the code the agent wrote, more in what it left at default: an open route, a fallback secret. do your red team agents read the config too, or just the PRs?
@0xFlydev an allocation checker with 23k views is the first page someone clones. "no TGE yet" on the real one is a good tell, the fake ones will say claim now.
Across lost its domain last week through a registrar support desk. One user lost ~$305K signing on the real URL.
Drop your project's site below. I'll check it from the outside, the way an attacker would, and DM you the 3 things I'd lock first.
Free. Passive checks only, nothing that touches your servers.
@StraySocietyRH "only use the link we post on launch day" is the right call. it also means on nov 18 your own domain becomes the single most valuable thing to hijack. is the registrar locked down for launch week?
@sardorml nice launch. the scary part of instant share links is what people record: admin panels, .env files, stripe dashboards. how long does a link live by default?
@starter_story $14K/month on supabase with zero prior coding means row level security was written by the same AI that wrote the features. worth one afternoon of someone trying to read other users' data
@floatdotxyz your real domain getting flagged together with the clone is the part nobody plans for. Google is quick to clear it, wallet blocklists usually aren't
@nunet_global two portals on two different domains with no deadline is a very long window for lookalike claim sites. pin the exact URLs before the reply bots show up
GitHub wasn't hacked this week. 4,837 developers' tokens were.
The scary part: 10,431 of those pushes landed in repos the account didn't even own. Collaborator access.
5-minute check: who still has write access to your org? Every old contractor counts.
(data: @AikidoSecurity)
@OfirEhrlich seven seconds is the part to sit with. by the time anyone opens that PR, the secrets are already gone. the only defense that works at that speed is fewer people holding tokens that can write
@IntCyberDigest the number that scares me isn't 61,000. it's 10,431: pushes into repos the account didn't even own, through collaborator access. every old contractor still on your org is one stolen token away
@aniel_cohen@AcrossProtocol the uncomfortable part: after this I checked 250 DeFi domains. 34 sit at the same registrar, and not one has a registry lock. the fix costs less than a single audit day
@krishgandhi1806 1,000 users in 4 days is also when bots find your signup and upload endpoints. worth a rate limit before #62 turns into a free image host