GitHub Trends
Project Radar
- Blue team tool0xDanielLopez/TweetFeedRepo · 694 stars
- Blue team toolphishdestroy/destroylistHTML · 2,092 stars
- Blue team toolsjhgvr/oisdRepo · 272 stars
Research DeskLatest Research: October 15, 2026News Feed Refresh: October 26, 2026Radar Refresh: October 26, 202664 research entries
Independent Research Desk
Phishing Tradecraft · Infrastructure · Detection Engineering
PhishPond researches how modern phishing operations are built, run, and detected — campaign evolution, adversary infrastructure, phishing kits, OAuth and device-code abuse, AiTM frameworks, and the detection and validation workflows that catch them.
Recurring Intel
Attack-Side Tradecraft
Campaign tradecraft, lure mechanics, adversary infrastructure, identity pressure, and operator workflows worth modeling.
12 attack-side readsDetection Engineering
Detection engineering, telemetry analysis, reporting workflows, and validation that security teams can operationalize.
34 detection readsAPT Tradecraft
Emerging procedures, tooling, initial-access patterns, and cross-team tradecraft from real-world actor reporting.
18 tradecraft readsGitHub Trends
Lead Research
Enrollment urgency is the oldest helpdesk pretext wearing a new word. The objective is still a session token, and the tell is still Graph.
Microsoft tracked Storm-3121 and Storm-3032 running passkey-themed helpdesk calls since May 2026. The passkey narrative is a pretext that routes victims into AiTM and device-code flows — and the detection lives in what happens after the token lands, not in the lure.
Read more:Microsoft Security BlogBleepingComputer
Live Collection
Read more:BleepingComputer
Read more:Microsoft Security Blog
Read more:Dark Reading
Read more:Malwarebytes Labs
Read more:BleepingComputer
TweetFeed collects Indicators of Compromise (IOCs) shared by the infosec community at Twitter. Here you will find malicious URLs, domains, IPs, and SHA256/MD5 hashes. 694 stars.
Open project:GitHub
#blueteam#malware#malware-detection#malware-research
Real-time phishing & scam domain blocklist - 205k+ curated threats, 1M+ community, free API, multiple formats Primary language: HTML. 2,092 stars.
Open project:GitHub
#anti-phishing#blacklist#blocklist#crypto-scam
oisd blocklist 272 stars.
Open project:GitHub
#adblocking#adblocking-dns#adblocking-list#adblocklist
🐟 PhishTank Blocklist for Pi-hole Primary language: Shell. 13 stars.
Open project:GitHub
#blocklist#hosts#phishing#pihole
Zeek-Formatted Threat Intelligence Feeds Primary language: Zeek. 405 stars.
Open project:GitHub
#malware#phishing#threat-intelligence#threatintel
Coverage Map
Specific campaigns, actor activity, and the lures behind them.
How techniques work end-to-end — walkthroughs and operator workflows.
Adversary infrastructure: kits, AiTM, redirectors, and sending abuse.
Detection engineering, telemetry, validation, and response.
Longer research notes, measurement, and periodic briefs.
Search Tool
Search titles, authors, tags, and body text across the PhishPond research archive.
Showing 5 matching entries.Clear search
Field Analysis
A static permission review cannot catch a trusted integration whose token is later stolen or whose behavior changes.
Read more:The Hacker NewsMicrosoft Learn
Field Analysis
Restricting new consent is only half the work. Existing app grants need review, ownership, and a path to removal when risk changes.
Read more:Microsoft LearnMicrosoft Learn
Field Analysis
The Salesloft Drift incident showed how a trusted integration token can become an access path into customer SaaS data without a fresh user login.
Read more:The Hacker NewsThe Hacker News
Field Analysis
Persistent OAuth grants let third-party apps keep operating after the original login, password reset, or employee lifecycle event has faded from view.
Read more:The Hacker NewsMicrosoft Learn
Field Analysis
OAuth app grants accumulate over time, and stale consent can become a hidden access path when vendors, users, or integrations are later compromised.
Read more:Microsoft LearnThe Hacker News