Auditing high-impact distributed infrastructure, dissecting enterprise logic flaws, and uncovering critical zero-day vulnerabilities across modern codebases.
0
Advisories · CVE / GHSA
0
Accreditations
0
CTF Engagements
Open
For Security Audits
Security Disclosures
Research & CVEs
Credentials
Certificates
Competitive Operations
Capture The Flag
Track Record
Experience
Selected Work
Projects
Certificate
Control Center · ciprobe
Administrator Access
Enter your password to manage records.
Local-only console. Authentication and data live in this browser's storage — a convenience lock, not a server security boundary.
Research · CVE / GHSA / VDP / Hall of Fame
ID
Title
Severity
Date
Actions
Home page · hero text & marquee
Projects
Name
Stack
Year
Actions
Certifications
Title
Issuer
Image
Year
Actions
CTF Competitions
Event
Result
Image
Year
Actions
Experience
Role
Organization
Period
Actions
Profiles & Handles (feed the hero links)
Platform
Handle
URL
Actions
Export & restore
Download the full portfolio as a portable JSON file, or restore from one. Imported data is validated and sanitized field-by-field.
Admin access path
This panel has no visible button. It opens only when the page URL ends with your secret path, then the path is wiped from the address bar. Keep it private.
open with ciprobe.uz/hakerpromaxultragalaxy
Change password
Password is stored only as a salted SHA-256 hash in this browser. It is never kept or shown in plaintext.
Reset admin lock
Forgot the password? Clear the stored credential and set a new one on next unlock. Portfolio data is not deleted.
Hardening on this static page: no inline event handlers, every rendered value HTML-escaped, URLs restricted to http/https/mailto (images also allow inline data:, uploads re-encoded via canvas to strip payloads), salted SHA-256 password with escalating attempt lockout, auto-lock after 10 min idle, strict Content-Security-Policy. What a static file CANNOT do: rate-limit traffic or stop a DDoS, nor hide data from someone with developer-tools access to this browser — those need the hosting layer (CDN / WAF / reverse proxy) and a real backend with server-side auth.