CASE 001 / PUBLIC DISCLOSURE / CRITICAL
DISCLOSEDBridged funds can become permanently locked.
Overlayer SC DualDefense Audit: an _credit() underflow can revert the hub receive path.
SFTWR LABS / LED BY 0xSFTWR
Independent security research studio
Security research, focused code reviews, and proof-of-concept work for complex software. Find the failure. Prove the impact. Understand the fix.
SCOPED REVIEWS + RESEARCH COLLABORATIONS
FIG. 01 — SYSTEM STUDY
Security research, reverse engineering, and careful deconstruction.
Hover to inspect. Click to reconstruct.
01 / RESEARCH / SELECTED WORK
A small, independent lab examining the boundaries between code, permissions, and value. The work starts with a question and ends with evidence that can be reproduced.
Led by Stefany Dos Santos / 0xSFTWR, with a background in programming and network security. Independent research across application security and Web3.
B.A.S. in Network Security & Forensics and an A.S. in Programming from Palm Beach State College. CompTIA Security+ and Network+. Research tools include Python, Solidity / Foundry, JavaScript, Git and Linux.
Researcher résuméCASE 001 / PUBLIC DISCLOSURE / CRITICAL
DISCLOSEDOverlayer SC DualDefense Audit: an _credit() underflow can revert the hub receive path.
02 / FIELDWORK / ATTACK SURFACE INDEX
The useful bugs live where individually valid rules stop agreeing with one another.
Credits, debits, settlement, message paths, and finality.
BRIDGE / OFT / PROOFExecution, margin, intent, pricing, and position transitions.
POSITION / MARGIN / INTENTQueues, refunds, retries, unwind, and value already in flight.
ESCROW / CLAIM / RECOVERYAllowances, permissions, blocklists, and cross-call identity.
AUTH / IDENTITY / STATE03 / EVIDENCE STANDARD / CONTROL BEFORE CLAIM
Every candidate has to survive the same-state control, full-lifecycle economics, and the final recovery state.
Same balances. Same claims. Same authority. Same market.
Not convenient calldata—the best executable recovery or intended path.
Setup, capital, maintenance, gas, helpers, unwind, and recovery.
Victim assets, attacker wealth, debt, claims, reserves, and final state.
04 / PUBLIC ARCHIVE / INSPECTABLE SOURCES
No filler projects. Only public artifacts that can be opened and checked.
PRIMARY RECORD
↗ SRC_002PROCESS NOTES
↗ SRC_003DIAGNOSTIC HARNESS
↗The methodology and CosmWasm repositories are research artifacts. The CosmWasm report was closed on asset-scope grounds; it is not an additional accepted finding.
WORK WITH SFTWR LABS / RESEARCH + REVIEWS
Start with a repo or system overview, the question you need answered, and your timeline. The lab takes on focused security reviews, vulnerability validation, and research collaborations with a clear scope.
Authorization boundaries, smart-contract logic, or a specific value flow. A written scope, reproducible tests, and findings you can act on.
Reproduce a reported issue, test its impact, and check the proposed fix with control and regression tests.
Work alongside an audit or engineering team on source review, test harnesses, and clear technical reporting.
Independent studio · Florida, US · Async first