News for hackers. Stuff that matters.

charlieekelly

I built a small tool called Trawler (part of PhishDeck) to remove the most tedious part of handling suspicious emails: extracting IOCs and getting reports ready to send quickly.

What it does: upload a suspicious email (.eml / .msg) or paste the email HTML, it extracts indicators (URLs/domains/etc), summarises what it found, then generates an abuse/report pack and helps you submit reports to relevant parties (hosting providers, domain registrars, and other trackers) in one go.

What it does not do: it does not click or detonate any links from the email, and it does not collect/report/log anything unless you explicitly hit submit.

I’d value blunt feedback from folks who deal with email abuse or IR: what’s missing, what feels clunky, and which reporting destinations you’d want added (or avoided)?

Cheers, Charlie

Advanced phishing attacks are becoming increasingly commonplace with tools that allow attackers to harvest credentials, bypass Two-factor authentication (2FA), as well as run automated post-exploit scripts the instant you enter your credentials. This post takes a look at our journey towards releasing Phinn, the real-time phishing simulation proxy that sits at the core of the PhishDeck phishing simulation platform.