Skip to content
View mehulpatel23b-pixel's full-sized avatar
  • India

Block or report mehulpatel23b-pixel

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
security engineering with a blue-team bias

Mehul Patel

Security engineering · attack-surface auditing · detection tooling

I build small, offline, zero-dependency tools that answer one question about an environment: where can an attacker actually go from here, and what is the shortest fix?

Every tool reads configuration and logs instead of attacking anything, proves the exposure with evidence, and prints the exact change that closes it.

profile views based in India offline first zero runtime dependencies MIT licensed


▸ Coverage

Domain Exposure it finds Tools
Cloud & identity IAM privilege-escalation primitives, CloudTrail identity attacks correlated across principals, CI secrets ranked by real reach escalens · trailtriage · ciradius
Active Directory Live NTLM relay paths from coercion source to target, and the fewest changes that kill the most of them relaymap
Kubernetes & containers RBAC hops from any subject to cluster-admin, Dockerfiles that bake in secrets or finish as root rbacpath · dockseal
Network & host sshd config as sshd would actually apply it, brute-force and spray chains in auth logs, pcap traffic with scans and C2 beacons sshsurface · bruteradar · packetlens
Email, web & DNS Phishing and BEC in raw mail, lookalike URLs, SPF/DMARC spoofability, missing security headers mailcase · phishverdict · spoofscope · hdrscope
AI & agent security Risky MCP server config, prompt injection in files and scraped content, ambiguous LLM tool definitions, agent skill leaks mcpseal · injectguard · toolcheck · skill-doctor
Detection engineering How noisy a Sigma rule will be on real logs, duplicate alerts fused into one explainable incident queue sigmanoise · alertfuse
Supply chain & CI Typosquatted packages, unpinned workflow actions, secrets that were ever committed to git pipxray · wfshield · pastsecrets

Plus autonomous multi-agent security crews for triage, threat modeling and patch response: sentinel-swarm · threatweave · patchswarm


▸ Featured work

escalens trailtriage

mcpseal wfshield

sshsurface packetlens


▸ How I build

[1] offline         no network calls, no cloud API, no credentials to hand over
[2] zero deps       pure Python standard library, so the auditor has no supply chain of its own
[3] explainable     every finding carries evidence, attack reason and the exact fix
[4] CI-gated        stable exit codes and JSON output, drops straight into a pipeline
[5] read-only       it reads config and logs, it never touches the target

A finding you cannot explain is a finding nobody fixes. So each result looks like: what is exposed → why it matters → the line to change.


▸ Toolbox

Languages & data

Python Bash YAML JSON Markdown

Platforms & pipelines

Linux Docker Kubernetes AWS GitHub Actions Git

Security domains

AWS IAM CloudTrail NTLM relay Kubernetes RBAC OpenSSH pcap triage Sigma SOC triage SPF DMARC phishing analysis MCP security prompt injection supply chain CI hardening


▸ Signal

GitHub stats Top languages

Contribution streak

Contribution graph


▸ Phishing triage suite

A reported phish moves through five questions. There is a tool for each, and all of them run offline.

Stage Tool The question it answers
Link in the mail redirectchain Where does the chain really end, and where does the trust break on the way
Page saved by a user formguard Where does the password post, does the brand match the host, what exfiltrates
Attachment forwarded attachscan What the file really is, past the extension: macro, smuggling, encrypted zip, LNK
Thread escalated becscan Who is actually in the conversation: name reuse, lookalike domain, bank change
Domain being imitated typosquat Which lookalike domains exist right now, and which technique built them
Impersonation already live dmarcrpt Which IPs send as your domain and fail both DKIM and SPF

Older triage pieces that pair with the suite: mailcase (raw mail, 57 checks) · phishverdict (URL scoring) · spoofscope (SPF/DMARC posture) · hdrscope (security headers)


▸ Ethics

Everything here is defensive and read-only: config auditors, log analysers and posture graders. There is no exploitation code, no traffic generation and no credential harvesting. Run them against systems you own or have written authorisation for. Findings stay on your machine.

Assessment work, collaboration, or a tool you want built? Open an issue on any repo or send a DM here on GitHub.

contribution grid

Offline by default. Explainable by design. MIT licensed.

Pinned Loading

  1. phone-intel phone-intel Public

    CLI tool that finds publicly available information from a mobile number: validity, country, carrier, line type, timezone, and public directory lookups

    Python 1