Title of the featured article
Two or three sentences: what was studied, what was found, why it matters.
by Author NameRead research →
BYTE41 SECURITY / INDEPENDENT RESEARCH TEAM
Security research.Real-world testing.
We investigate application security weaknesses and help software teams understand, fix, and verify them.
FOCUSWeb · API · Source code
METHODManual, research-led
POLICYWritten authorization required
0x01 / SELECTED RESEARCH
Selected research
> Research in progress.
Our published findings and technical notes will appear here.
Title of the second article
One or two sentences of summary.
by Author NameRead research →
Title of the third article
One or two sentences of summary.
by Author NameRead research →
0x02 / PUBLIC FINDINGS
Public findings
| IDENTIFIER | FINDING | AFFECTED PRODUCT | DISCLOSURE DATE | REFERENCE |
|---|
> No public findings yet.
Disclosed findings will be listed here with links to public references.
// Products listed in this table are subjects of independent research. They are not Byte41 clients.
0x03 / SERVICES
Work with Byte41.
01
Web Application Penetration Testing
Manual testing of authentication, authorization, session handling and business logic in web applications.
- TYPICALLY IN SCOPE
- Login, session and account recovery flows
- Access control between roles and between tenants
- Injection, cross-site scripting and server-side request forgery
- File upload and download handling
- Abuse of business rules such as pricing, limits and workflows
02
API Security Testing
REST and GraphQL endpoints tested for broken access control, injection and unintended data exposure.
- TYPICALLY IN SCOPE
- Object-level and function-level authorization
- Token, key and session handling
- Mass assignment and excessive data exposure
- Rate limiting and resource abuse
- GraphQL introspection, batching and query depth
03
Source Code Review
Review of security-critical code paths, with each finding traced to the exact source location.
- TYPICALLY IN SCOPE
- Authentication and authorization logic
- Input validation and output encoding
- Use of cryptography and handling of secrets
- Risky third-party dependencies and how they are used
0x04 / THE TEAM
The team
@handle
[Researcher name]
[ROLE]
FOCUS[Specialty] · [Specialty] · [Specialty]
[Two lines: research focus, background, and the kind of systems this person tests.]
@handle
[Researcher name]
[ROLE]
FOCUS[Specialty] · [Specialty]
[Two lines: research focus, background, and the kind of systems this person tests.]
// Profile links show participation only and do not imply endorsement by any platform.
0x05 / ABOUT
Research first, then testing.
Byte41 Security is an independent security research team offering penetration testing and source code review. What we learn from studying real software shapes how we test yours.
- 01
Scope
Targets, depth, timing and rules of engagement, agreed in writing.
- 02
Test
Manual testing against the agreed scope. Critical issues are reported as they are found.
- 03
Report
Each finding documented with impact, evidence and a recommended fix.
- 04
Retest
Once fixes are in, we verify them within the agreed scope.
0x06 / CONTACT
Tell us what needs testing.
Share the scope and your timeline. We reply with questions or a proposal.
EMAILhello@byte41.com
PGP[PGP KEY FINGERPRINT]