Eve library

Lilith Platform Threat Model

Guide

Revision 1

On this page

1. System Overview#

The Lilith Platform is a decentralized content licensing system with the following attack surfaces:

  • Smart Contracts: 4 core contracts + security modules
  • External Integrations: Marketplaces, oracles
  • User Interactions: Token purchases, license minting, staking
  • Admin Operations: Upgrades, fee changes, pausing

2. Asset Inventory#

High-Value Assets#

Asset Location Value Estimate Protection
User ETH in purchases AccessToken Variable Reentrancy guard, CEI
Creator royalties CreatorRoyalties Variable Pull payment pattern
Staked tokens IdentityReputation Variable Slashing rules
Platform fees Treasury Variable Multi-sig ownership
Content licenses ContentLicenseNFT Subjective Ownership tracking

Medium-Value Assets#

Asset Risk Protection
Reputation scores Manipulation Oracle + challenge
Contract ownership Takeover Ownable2Step, timelock
Upgrade authority Malicious upgrade UUPS + timelock

3. Threat Actors#

3.1 External Attackers#

Profile: Anonymous actors seeking financial gain or disruption

Capabilities:

  • Flash loan access (unlimited capital for 1 block)
  • Contract interaction (public functions)
  • Front-running transactions (MEV)
  • Multiple wallet usage (Sybil attacks)

Motivations:

  • Financial theft
  • Market manipulation
  • Competitive disruption

3.2 Malicious Users#

Profile: Registered users with legitimate access

Capabilities:

  • All public functions
  • Registered identity
  • Staking participation
  • Content submission

Motivations:

  • Gaming reputation system
  • Fraudulent content licensing
  • Fee avoidance

3.3 Compromised Admin#

Profile: Attacker with access to admin keys

Capabilities:

  • Contract pausing
  • Fee modification
  • Treasury changes
  • Upgrades (if timelock bypassed)

Motivations:

  • Fund extraction
  • Platform destruction
  • Ransom

3.4 Malicious Oracle#

Profile: Compromised oracle service

Capabilities:

  • Arbitrary reputation updates
  • Challenge resolutions
  • Score manipulation

Motivations:

  • Reputation attacks
  • Slashing victims
  • Collusion with users

4. Threat Analysis#

4.1 Smart Contract Vulnerabilities#

T1: Reentrancy Attacks#

  • Threat: Attacker re-enters function during external call
  • Impact: Fund drainage
  • Likelihood: LOW (mitigated)
  • Mitigation: ReentrancyGuard, CEI pattern, pull payments
  • Residual Risk: Minimal

T2: Flash Loan Attacks#

  • Threat: Attacker manipulates prices/votes within single block
  • Impact: Value extraction, governance manipulation
  • Likelihood: LOW (mitigated)
  • Mitigation: FlashLoanGuard blocks same-block actions
  • Residual Risk: Low

T3: Integer Overflow/Underflow#

  • Threat: Arithmetic errors leading to incorrect calculations
  • Impact: Incorrect payments, infinite tokens
  • Likelihood: VERY LOW
  • Mitigation: Solidity 0.8+ native overflow checks
  • Residual Risk: Minimal

T4: Access Control Bypass#

  • Threat: Unauthorized access to privileged functions
  • Impact: Admin takeover, fund theft
  • Likelihood: LOW
  • Mitigation: Ownable2Step, function modifiers, tests
  • Residual Risk: Low

T5: Upgrade Vulnerabilities#

  • Threat: Storage collision, malicious implementation
  • Impact: Complete fund loss, functionality break
  • Likelihood: MEDIUM (requires owner compromise)
  • Mitigation: Timelock delays, storage gap patterns
  • Residual Risk: Medium

4.2 Economic Attacks#

T6: Price Manipulation#

  • Threat: Manipulating token prices for profit
  • Impact: Unfair value extraction
  • Likelihood: MEDIUM
  • Mitigation: Creator-set prices, no on-chain price oracles
  • Residual Risk: Low (prices are fixed)

T7: Royalty Evasion#

  • Threat: Bypassing royalty payments
  • Impact: Creator revenue loss
  • Likelihood: HIGH (common issue)
  • Mitigation: Marketplace authorization, on-chain enforcement
  • Residual Risk: Medium (off-chain transfers possible)

T8: Sybil Attacks on Reputation#

  • Threat: Creating multiple identities to game reputation
  • Impact: Reputation system integrity
  • Likelihood: MEDIUM
  • Mitigation: Staking requirement, slashing mechanism
  • Residual Risk: Medium

4.3 Governance Attacks#

T9: Ownership Takeover#

  • Threat: Gaining control of owner role
  • Impact: Complete platform control
  • Likelihood: LOW
  • Mitigation: Multi-sig, Ownable2Step, monitoring
  • Residual Risk: Low

T10: Timelock Bypass#

  • Threat: Executing upgrades without delay
  • Impact: Malicious upgrade deployment
  • Likelihood: VERY LOW
  • Mitigation: Timelock has no bypass mechanism
  • Residual Risk: Minimal

4.4 Operational Attacks#

T11: Denial of Service#

  • Threat: Making contracts unusable
  • Impact: Platform downtime
  • Likelihood: MEDIUM
  • Mitigation: Pull payments, gas limits, pausing
  • Residual Risk: Low

T12: Front-Running#

  • Threat: MEV bots extracting value from pending transactions
  • Impact: User value loss
  • Likelihood: HIGH (inherent to Ethereum)
  • Mitigation: Limited applicability (fixed prices)
  • Residual Risk: Low (not applicable to most functions)

T13: Oracle Manipulation#

  • Threat: Feeding false data to reputation oracle
  • Impact: Unfair reputation changes
  • Likelihood: MEDIUM
  • Mitigation: Challenge system, multi-oracle (future)
  • Residual Risk: Medium

5. Trust Boundaries#

text
┌─────────────────────────────────────────────────────────────────┐
│                     TRUSTED (Internal)                           │
│  ┌─────────────┐  ┌─────────────┐  ┌─────────────────────────┐  │
│  │   Owner     │  │   Pauser    │  │        Oracle           │  │
│  │ (Multi-sig) │  │             │  │                         │  │
│  └─────────────┘  └─────────────┘  └─────────────────────────┘  │
├─────────────────────────────────────────────────────────────────┤
│                    TRUST BOUNDARY                                │
├─────────────────────────────────────────────────────────────────┤
│                    SEMI-TRUSTED                                  │
│  ┌─────────────┐  ┌─────────────────────────────────────────┐   │
│  │ Marketplaces│  │           Verifiers                      │   │
│  │ (Authorized)│  │                                          │   │
│  └─────────────┘  └─────────────────────────────────────────┘   │
├─────────────────────────────────────────────────────────────────┤
│                    TRUST BOUNDARY                                │
├─────────────────────────────────────────────────────────────────┤
│                     UNTRUSTED (External)                         │
│  ┌─────────────┐  ┌─────────────┐  ┌─────────────────────────┐  │
│  │   Users     │  │  Creators   │  │     Attackers           │  │
│  │             │  │             │  │                         │  │
│  └─────────────┘  └─────────────┘  └─────────────────────────┘  │
└─────────────────────────────────────────────────────────────────┘

Trust Assumptions#

  1. Owner is honest: Multi-sig with known parties
  2. Timelock works correctly: No bypass mechanism
  3. Oracle is accurate: Backend service with monitoring
  4. Ethereum is secure: No 51% attacks or reorgs

6. Attack Scenarios#

Scenario 1: Flash Loan Price Manipulation#

Attack Path:

  1. Take flash loan for 10,000 ETH
  2. Attempt to purchase large quantity of tokens
  3. Attempt to sell/stake in same block
  4. Profit from price impact

Outcome: BLOCKED by FlashLoanGuard

Scenario 2: Reentrancy on Withdrawal#

Attack Path:

  1. Deploy malicious contract
  2. Call withdrawal function
  3. In receive(), re-call withdrawal
  4. Drain funds before state update

Outcome: BLOCKED by ReentrancyGuard + CEI pattern

Scenario 3: Reputation Gaming#

Attack Path:

  1. Create multiple identities with minimum stake
  2. Have identities rate each other positively
  3. Gain unearned reputation

Outcome: MITIGATED by:

  • Oracle-controlled updates (not peer rating)
  • Minimum stake requirement
  • Challenge system for disputes

Scenario 4: Admin Key Compromise#

Attack Path:

  1. Compromise owner private key
  2. Attempt to drain treasury
  3. Attempt to upgrade with malicious contract

Outcome: DELAYED by:

  • 72h timelock on upgrades
  • Multi-sig requires multiple signatures
  • Monitoring detects ownership changes

Scenario 5: Malicious Upgrade#

Attack Path:

  1. Deploy malicious implementation
  2. Schedule upgrade through timelock
  3. Wait 72 hours
  4. Execute upgrade, drain funds

Outcome: DETECTABLE via:

  • On-chain monitoring alerts on CallScheduled
  • 72h window for investigation and cancellation
  • Bytecode verification before execution

7. Mitigation Summary#

Threat Risk Level Mitigation Status
Reentrancy LOW COMPLETE
Flash Loans LOW COMPLETE
Overflow VERY LOW COMPLETE
Access Control LOW COMPLETE
Upgrades MEDIUM PARTIAL (needs audit)
Price Manipulation LOW COMPLETE
Royalty Evasion MEDIUM PARTIAL (off-chain)
Sybil Attacks MEDIUM PARTIAL
Ownership Takeover LOW COMPLETE
DoS LOW COMPLETE
Front-Running LOW N/A
Oracle Manipulation MEDIUM PARTIAL

Short-Term (Pre-Mainnet)#

  1. External audit from tier-1 firm
  2. Formal verification of critical paths
  3. Extended testnet deployment
  4. Bug bounty program

Medium-Term (Post-Launch)#

  1. Multi-oracle implementation
  2. Governance decentralization
  3. Insurance fund
  4. Automated incident response

Long-Term (Mature Platform)#

  1. DAO governance
  2. Decentralized oracle network
  3. Cross-chain expansion
  4. Zero-knowledge identity proofs

9. Audit Focus Areas#

Priority areas for external auditors:

  1. HIGH PRIORITY

    • UUPS upgrade mechanism
    • ETH handling in all contracts
    • Access control implementation
    • Reentrancy protection coverage
  2. MEDIUM PRIORITY

    • Flash loan guard effectiveness
    • Staking/slashing logic
    • Pull payment pattern
    • Fee calculation accuracy
  3. LOWER PRIORITY

    • Gas optimization opportunities
    • Event emission completeness
    • Documentation accuracy
    • Test coverage gaps