crytic / crytic/slither

Add support to detect functions that return `msg.sender` via direct or aliased return values

Open
#2,755 0 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Python
Stars
6.4k
Forks
1.1k
PR merge metrics
No merged PRs in 30d

Description

### Describe the desired feature

Introduce support in Slither to detect Solidity functions that return `msg.sender`, either directly or through transitive variable aliasing

## Motivation
Static analysis often requires understanding the flow of `msg.sender`—especially in:
- Authorization checks
- Meta-transaction handling (_msgSender() patterns)

Being able to detect whether a function returns `msg.sender`, even through variable aliasing, is a foundational capability for writing detectors related to access control, trust boundaries, and function exposure.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.