About
Run by a researcher who still writes the PoCs.
I started MemCyber after one engagement: a fintech that had paid two prior firms for pentests and still had a critical authorization flaw in production. I delivered the finding in a morning. The report came back with a working exploit and a one-line fix. That is still how the firm works.
I’m Atilla Mammadli — a security researcher with a long record on public and private bug bounty platforms, smart contract contests, and independent web application assessments. I still write every PoC personally. That is where the signal is.
Every engagement is run by the same senior researcher who scoped it. No junior hand-offs. No subcontractors. That constraint is the trade-off: it lets us move fast, read code carefully, and find the bugs that scanner-driven pipelines miss.
Credentials
- Ranked contributorCantina & Sherlock audit contests
- HackerOne triage history50+ valid reports across private programs
- Responsible disclosureCoordinated with fintech, crypto, and SaaS vendors globally
- Speaker / WriteupsTechnical writeups on IDOR, oracle manipulation, KYC bypass
Platforms & Programs
Since 2022
A short track record.
Independent research to full firm, one public milestone at a time.
- 22 2022First HackerOne submissionStarted independent research on public bug bounty programs.
- 23 2023Smart contract entryFirst Solidity audit contest contribution on Cantina and Sherlock.
- 24 2024First private engagementFirst paid pentest for a fintech — disclosed a critical authorization flaw two prior firms had missed.
- 25 2025Continuous retainer modelLong-term retainer engagements across fintech and Web3.
- 26 2026MemCyber foundedIndependent firm launched. Same commitment: senior researcher on every engagement, no subcontractors.
Expertise
Depth across the surfaces attackers care about.
We specialize in the intersection of application, protocol, and on-chain security — the boundary where the hardest bugs live.
How we operate
Values that shape every engagement.
Evidence over opinion
Every finding ships with a working proof-of-concept. If we say it is exploitable, we show you how — and we stop calling it a finding if we cannot.
Signal over noise
We don't pad reports with scanner output, missing headers, or "informational" filler. You get the findings that actually change your risk posture.
Engineer-first reports
Reports are written for the person who will fix them. Executive summary for leadership, root-cause and remediation for engineering.
Responsible by default
All testing runs under written authorization. Scope is respected. Findings go through coordinated disclosure. Always.