┌─────────────────────────────────────────────────────────────────┐
│  whoami                                                         │
│  > Independent vulnerability researcher · Pakistan             │
│  > Specialization: Memory corruption · Firmware · Embedded      │
│  > Disclosure model: 90-day responsible · CVE author           │
│  > Status: Open to consulting · Research collaboration          │
└─────────────────────────────────────────────────────────────────┘

I hunt bugs at the intersection of C/C++ memory safety, embedded firmware, and RTOS attack surfaces — the layer most researchers skip. My work targets real-world impact: RCE chains, privilege escalation, and trust boundary violations in hardware-adjacent code.

• Core specialties: Heap/stack corruption · Integer overflows · Path traversal chains · Firmware reverse engineering · Vulnerability chaining
• Target surfaces: Embedded Linux · RTOS (RT-Thread, Zephyr, FreeRTOS) · IoT firmware · Native libraries · SDK attack surfaces
• Methodology: Static + dynamic analysis · PoC-first · Coordinated disclosure with full write-up

All disclosures follow 90-day coordinated timelines aligned with Google Project Zero standards.

current_targets = [
    "Embedded RTOS surfaces (RT-Thread · Zephyr · FreeRTOS)",
    "Native library heap internals (LevelDB · RocksDB · SQLite)",
    "Firmware supply chain integrity",
    "SDK / toolchain attack surfaces",
]

programs = ["Google OSS VRP", "MSRC", "Intel/Intigriti", "ZDI (pipeline)"]

[!] No PoC, no report.
[!] Vendor silence past 90 days triggers coordinated public disclosure.
[!] Severity is what the attacker can do — not what the vendor wants to hear.
[!] The best bug report is one the engineer can act on in 10 minutes.