
A developer recently conducted an experimental study by creating a Rust-based executable designed to report on the environments where it was executed. By submitting the binary to VirusTotal, the author collected telemetry data, including OS versions, hardware specifications, and process information, via DNS heartbeats and HTTPS dossiers. The experiment aimed to reverse the traditional malware analysis workflow, where a sandbox usually observes a program. Instead, the program observed the sandbox. The collected data revealed interesting patterns, such as how different analysis environments renamed the file or handled network requests. The author visualized the findings in a project called WAYPOINT, which maps the telemetry data to provide insights into how various services interact with unknown binaries. While the study provides a unique look at environment fingerprinting, the author notes that the results are based on heuristics and do not definitively identify specific sandbox operators or infrastructure.
This is a summary. Read the full article at the original source:
Dev.toRelated stories
I built an honest CS2 case opening site — and realized why honesty changes nothing
A developer has created a fully functional, open-source CS2 case opening site (CaseForge) to investigate how such platforms operate. The project featu…
Stop Wasting LLM Tokens! I Built a Rust CLI to Prune JS/TS Codebases by 80%
Developer Sanjaiyan has introduced 'urai-ecma', a high-performance Rust-based CLI tool designed to optimize JavaScript and TypeScript codebases for LL…
When an antibot pretends to be a regulator: false positives and local Web UI in rkn-block-checker 0.6.0
The rkn-block-checker CLI utility has been updated to version 0.6.0, improving its ability to diagnose network blocks. The tool analyzes failures acro…


