Phoenix Protocol

Rising from the ashes of vulnerabilities!

[Phoenix Protocol @ph0enixProtocol]

🚀 Day 0 / 15 — The Perim Framework

Starting today, we’re building the base of our ASM engine — Perim.

Not another recon script. A modular, security-engineering–grade recon framework that orchestrates capabilities.

[Phoenix Protocol @ph0enixProtocol]

This wasn’t luck — it was design.
Our new modules now include:
✅ Webapp Probing
✅ JS Surface Recon
✅ Filtering Engine
Each tuned to find signal, not noise — and to stop automatically when it matters.

#SecurityEngineering #BugBounty #Infosec

[Phoenix Protocol @ph0enixProtocol]

🚨 Responsible Discovery Drop — During internal testing of the Perim ASM Framework, we surfaced a critical exposure responsibly while validating our new JS Recon + Webapp modules.
Here’s how engineering + ethics came together 👇
#perim #buildinpublic #AttackSurface

[Phoenix Protocol @ph0enixProtocol]

Check out the detailed engineering blog at
https://t.co/1uKkO5zkbo

[Phoenix Protocol @ph0enixProtocol]

Safety first: All probes default to non-destructive, scope-aware, and rate-limited modes.
We’re still invite-only for feedback. DM “perim-feedback” to discuss early review. Follow for Day 5 where we’ll add HTTP fingerprinting & JS URL analysis insights. #BugBounty #ASM #InfoSec

[Phoenix Protocol @ph0enixProtocol]

🚀 Day 3-4 / 15 — The Perim Framework
Perim progress update: port scanning, web probing, and our Perim crawler for URL discovery are now integrated into the pipeline. #BuildInPublic #perim

[Phoenix Protocol @ph0enixProtocol]

Why this matters: detecting what responds + what URLs exist turns raw discovery into actionable context. It reduces noise for hunters and gives teams a precise baseline for change detection. That’s where real findings start.

[Phoenix Protocol @ph0enixProtocol]

Why this matters:
Recon without context is noise. Now we see what exists and what responds — the first step toward meaningful diffs and prioritized findings.
Follow the build. DM “feedback” if you want to join early review (invite-only).
#BugBounty #ASM #SecurityEngineering

[Phoenix Protocol @ph0enixProtocol]

🚀 Day 1 / 15 — The Perim Framework

We shipped subdomain enumeration (passive + active) and light service probing. Building the spine of a living inventory.
#phoenixprotocol #perim

[Phoenix Protocol @ph0enixProtocol]

What we implemented today:
• Passive collectors (CT, passive sources)
• Active enumeration (permissioned DNS & bruteforce where allowed)
• Safe service probes for common ports — HTTP, HTTPS, SSH (non-destructive) All results normalized into a deduped asset inventory.

[Phoenix Protocol @ph0enixProtocol]

Follow along. Updates daily.
#BuildInPublic #phoenixprotocol #perim #ASM #BugBounty #attacksurfacemanagement

[Phoenix Protocol @ph0enixProtocol]

🚀 Day 0 / 15 — The Perim Framework

Starting today, we’re building the base of our ASM engine — Perim.

Not another recon script. A modular, security-engineering–grade recon framework that orchestrates capabilities.

[Phoenix Protocol @ph0enixProtocol]

We aren’t chasing screenshots. We’re building a repeatable security pipeline that scales.
Because attack surface monitoring isn’t a single tool — it’s a system of clarity.

Attack surface monitoring isn’t about collecting data — it’s about connecting signals that matter.