Update README.md

This commit is contained in:
S3N4T0R
2026-08-02 07:36:13 -04:00
committed by GitHub
parent 33bbe70ac1
commit 0233b7f057
+3
View File
@@ -114,6 +114,9 @@ Following the same communication model, I configured the bot with the **Display
To enable BEAR-C2 to communicate with the Telegram account controlling the bot, I generated a Telegram **API ID** and **API Hash** through Telegram's developer portal. After registering a new application, these credentials were configured inside BEAR-C2, allowing the framework to authenticate and interact with the Telegram account used throughout the simulation. To enable BEAR-C2 to communicate with the Telegram account controlling the bot, I generated a Telegram **API ID** and **API Hash** through Telegram's developer portal. After registering a new application, these credentials were configured inside BEAR-C2, allowing the framework to authenticate and interact with the Telegram account used throughout the simulation.
<img width="1359" height="617" alt="image_(2)" src="https://github.com/user-attachments/assets/06dc25d6-b554-44bc-be88-b07796ba7642" />
`CHAR.cpp Configuration` `CHAR.cpp Configuration`
The final stage consisted of configuring the Telegram communication module inside **CHAR.cpp**. The **Bot Token** generated by BotFather was embedded into the agent, allowing it to authenticate with the Telegram Bot API and establish bidirectional communication with the operator. The final stage consisted of configuring the Telegram communication module inside **CHAR.cpp**. The **Bot Token** generated by BotFather was embedded into the agent, allowing it to authenticate with the Telegram Bot API and establish bidirectional communication with the operator.