From 0233b7f057a168f903b7b54341e0683a2ca8c458 Mon Sep 17 00:00:00 2001 From: S3N4T0R <121706460+S3N4T0R-0X0@users.noreply.github.com> Date: Sun, 2 Aug 2026 07:36:13 -0400 Subject: [PATCH] Update README.md --- Iranian APT/Charming Kitten/README.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/Iranian APT/Charming Kitten/README.md b/Iranian APT/Charming Kitten/README.md index a7f3dcf..9dd964d 100644 --- a/Iranian APT/Charming Kitten/README.md +++ b/Iranian APT/Charming Kitten/README.md @@ -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. +image_(2) + + `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.