Credential Harvesting with Telegram API, (Tue, Oct 4th)

This post was originally published on this site

[This is a guest diary by Jesse LaGrew]

Phishing emails are a daily occurrence and many times it ends with credential harvesting. An email initially lures a user to a website that promised an anticipated file. The landing page taunts a user to click on an additional link and enter their credentials. In this case, the credentials entered by the user are not sent back to the bad actor using a simple web form but using the Telegram API [1]. 

Phishing Landing Site ScreenFigure 1: Phishing Landing Site Screenshot

Looking at the source of the website, the URL encoding can make the text difficult to read. 

URL Encoded Text Screenshot from Document Source

Figure 2: URL Encoded Text Screenshot from Document Source

Within the URL decoded text, the destination for the input credentials can be found.

Telegram API URL for Credential SubmissionFigure 3: Telegram API URL for Credential Submission

Using the Proxy Intercept feature of Burp Suite can help to show the full Telegram API request. The response can also give some additional information about the bot account being used. 

Telegram API Request in Burb SuiteFigure 4: Telegram API Request in Burb Suite

Using the Telegram API for exfiltration is becoming much more common and API usage on your network may be a useful indicator. More information about this particular landing page can be found at URLScan [2]. 

Indicators

https://bitter-poetry-5215.westofsdfdsfd.workers[.]dev/
salmangreyBot (Telegram Bot)

[1] https://core.telegram.org/bots/api
[2] https://urlscan.io/result/c68bdef7-613b-4bad-a7fa-25c353842147/
 

(c) SANS Internet Storm Center. https://isc.sans.edu Creative Commons Attribution-Noncommercial 3.0 United States License.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.