Contact

For authorized application security consulting, source-code review, or a focused security assessment, email:

duyytrann22@gmail.com

When possible, include:

• product or repository context
• technology stack
• requested scope
• available test environment
• target timeline
• any known security concerns or constraints

This makes it easier to determine whether the engagement is a good technical fit and to define clear testing boundaries.

---

Public Profiles

• GitHub
• HackerOne
• Google Bug Hunters
• PT Security DBugs
• LinkedIn

For public vulnerability research and CVE write-ups, see the Research page.

---

Scope & Ethics

I only perform security testing in authorized environments, client-approved scopes, local labs, or public vulnerability-disclosure programs.

For consulting work, active testing should begin only after the target, environment, accounts, and testing boundaries are agreed.