SFTWR LABS / LED BY 0xSFTWR

Independent security research studio

SoftwareArchaeology

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

Understanding how systems work.

Security research, reverse engineering, and careful deconstruction.

Hover to inspect. Click to reconstruct.

System study
ACROSS PROGRAMS25+ PAID FINDINGS HACKENPROOF · 21 OCT 2026TOP 100 / #80 RESEARCH FOCUSCODE / PROTOCOLS WORKING STYLEASYNC / US BASED

01 / RESEARCH / SELECTED WORK

Research,
in practice.

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.

Founder background + résumé

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

DISCLOSED

Bridged funds can become permanently locked.

Overlayer SC DualDefense Audit: an _credit() underflow can revert the hub receive path.

HUB RECEIVE_CREDIT UNDERFLOWFUNDS LOCKED
WITHHELD BY DISCLOSURE POLICY WITHHELD BY DISCLOSURE POLICY WITHHELD BY DISCLOSURE POLICY

02 / FIELDWORK / ATTACK SURFACE INDEX

Hostile
state.

The useful bugs live where individually valid rules stop agreeing with one another.

  1. 01

    Cross-chain accounting

    Credits, debits, settlement, message paths, and finality.

    BRIDGE / OFT / PROOF
  2. 02

    Perps + order flow

    Execution, margin, intent, pricing, and position transitions.

    POSITION / MARGIN / INTENT
  3. 03

    Committed-value recovery

    Queues, refunds, retries, unwind, and value already in flight.

    ESCROW / CLAIM / RECOVERY
  4. 04

    Authority composition

    Allowances, permissions, blocklists, and cross-call identity.

    AUTH / IDENTITY / STATE

03 / EVIDENCE STANDARD / CONTROL BEFORE CLAIM

Mechanics are
not impact.

Every candidate has to survive the same-state control, full-lifecycle economics, and the final recovery state.

  1. 01 / SHARED STATE

    Freeze the moment before the disputed action.

    Same balances. Same claims. Same authority. Same market.

  2. 02 / TRUTHFUL CONTROL

    Run the strongest protocol-valid alternative.

    Not convenient calldata—the best executable recovery or intended path.

  3. 03 / ATTACK PATH

    Execute the full lifecycle.

    Setup, capital, maintenance, gas, helpers, unwind, and recovery.

  4. 04 / INCREMENTAL HARM

    Reconcile what the bug alone changed.

    Victim assets, attacker wealth, debt, claims, reserves, and final state.

04 / PUBLIC ARCHIVE / INSPECTABLE SOURCES

Open
record.

No filler projects. Only public artifacts that can be opened and checked.

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

Have something
worth breaking?

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.

01 / REVIEW

Focused security review

Authorization boundaries, smart-contract logic, or a specific value flow. A written scope, reproducible tests, and findings you can act on.

02 / VALIDATE

PoCs + fix verification

Reproduce a reported issue, test its impact, and check the proposed fix with control and regression tests.

03 / COLLABORATE

Research support

Work alongside an audit or engineering team on source review, test harnesses, and clear technical reporting.

sftwrlabs@gmail.com

Independent studio · Florida, US · Async first