Doggie and evilDoggie Project Overview

Doggie is an open-source, modular project designed to build a DIY CAN Bus to serial adapter (USB, BLE, UART). It connects your computer to a CAN Bus network using the slcan protocol (CAN over Serial) for compatibility with tools like SocketCAN and Python-can. The project emphasizes modularity, supporting various microcontrollers (e.g., RP2040, STM32F103C8, ESP32) and CAN controllers (built-in or MCP2515).
evilDoggie is the offensive firmware variant of Doggie, tailored for automotive security research and low-level CAN Bus manipulation. It enables advanced attacks like spoofing, bus off, double receive, and physical-layer overrides, making it ideal for red teaming and vulnerability testing in simulated or real CAN environments.
Developed by Faraday Security, the project was presented at Black Hat Arsenal on August 6-7, 2025, in Las Vegas. Both variants are open-source under the MIT License and available on GitHub at https://github.com/infobyte/doggie. Use responsibly for research and training only.
For detailed introductions, see the sub-sections for Doggie and evilDoggie.
Disclaimer
This project is a work in progress, and contributions are highly encouraged! While it is functional, some features may still be under development.
If you encounter issues or have suggestions for improvements, please feel free to open an issue or submit a pull request.
⚠ Doggie and EvilDoggie tools are provided for educational and research purposes only. By participating, you acknowledge that any testing, experimentation, or use of these tools on real vehicles or production systems is solely your responsibility. The authors and organizers do not accept any liability for damage, malfunction, legal consequences, or safety issues that may result from misuse, incorrect configuration, or applying these techniques outside of a controlled environment. Please use responsibly, and always test only on systems you own or have explicit permission to test.
License
This project is licensed under the MIT License. See the LICENSE file for details.