Rules › Solidity
Return value of a low-level call is ignored
call, send and delegatecall return false instead of reverting; ignoring it loses failures silently.
Why it matters
Low-level call, delegatecall, staticcall and send don't revert when the callee fails; they return false. Ignoring the result means a failed payment or call is treated as success, so accounting drifts from reality: users are marked paid when they weren't, or a step silently doesn't happen.
Vulnerable
function ping(address target) external {
target.call(abi.encodeWithSignature("ping()"));
}
Fixed
function ping(address target) external {
(bool ok, bytes memory ret) = target.call(abi.encodeWithSignature("ping()"));
if (!ok) revert CallFailed(ret);
}
What other tools call it
| Tool | Detector or reference |
|---|---|
| Slither | unchecked-lowlevel, unchecked-send |
| Solhint | check-send-result |
| Aderyn | unchecked-low-level-call |
| SWC registry | SWC-104 |
Check your code
Paste a contract into the in-browser checker, or let the Claude Code plugin scan before every deploy. The quick check for this rule is a pattern match: treat a hit as "look here", and a miss as no guarantee.
Related rules
- tx.origin used for authorization
- State written after an external call (reentrancy)
- delegatecall to an address the caller controls
- Initializer anyone can call
- Privileged function without access control
- selfdestruct in contract code
Static analysis finds known bug classes; it can't prove code is safe and isn't an audit. Get a professional audit before deploying code that will hold value.