gommzystudio/device-activity-tracker

A phone number can reveal whether a device is active, in standby or offline (and more). This PoC demonstrates how delivery receipts + RTT timing leak...

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 36 minutes ago
Added to GitGenius on September 13th, 2026
Created on December 7th, 2025
Open Issues & Pull Requests: 34 (+0)
GitHub issues: Enabled
Number of forks: 703
Total Stargazers: 5,128 (+0)
Total Subscribers: 65 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 1.5 hours
Mean response time: 4.8 days
90th percentile: 9.1 days
Tracked items: 31

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 11% of issues opened in the past year have been closed. Three people close 67% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 19
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 222 days
Stale 30+ days: 19
Stale 90+ days: 18

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Device Activity Tracker is a proof-of-concept tool that demonstrates privacy vulnerabilities in WhatsApp and Signal by inferring device activity states from message delivery timing.

The tool exploits a privacy leak in how messaging applications handle delivery receipts. By sending probe messages and measuring the round-trip time of acknowledgments, it can detect whether a target device is actively in use, in standby mode, or offline. The approach works by analyzing the CLIENT ACK response time to probe messages, using a dynamic threshold calculated from median RTT values to classify device states. Two probe methods are available: sending delete requests or reaction emojis to non-existent message IDs, both of which trigger server responses without alerting the target user.

This is explicitly a proof-of-concept for security research and educational purposes, implementing research from academic work on messaging application vulnerabilities. Potential adopters should understand that this tool is designed to demonstrate a surveillance capability rather than solve a practical problem. It suits security researchers, privacy advocates, and developers studying messaging application vulnerabilities. The project includes both a web interface for real-time monitoring and a command-line interface, with Docker deployment available for ease of setup.

The project shows active development with implementations across multiple technology layers: a Node.js backend using the Baileys library for WhatsApp integration, a React frontend for visualization, and TypeScript throughout for type safety. The codebase demonstrates attention to practical deployment concerns through Docker support and configurable port settings. The tool includes adaptive threshold logic that adjusts to different network conditions rather than using fixed timing values, suggesting iterative refinement based on real-world testing scenarios.