Public
- Public
- Network
- Groups
- Featured
- Popular
- People

Conversation

Notices

Embed this notice
Brian Clark (deepthoughts10@infosec.exchange)'s status on Monday, 17-Feb-2025 06:39:52 JST Brian Clark
- Christoffer S.
If you help maintain #cybersecurity on a business network you should absolutely block Telegram—there’s nothing good there. If you have a web security proxy like Netskope or Zscaler, or an NGFW, block it there. You can also block it via DNS. Blocking these domains should do the job:
telegram.me
telegram.org
t.me
cdn-telegram.org
telegram-cdn.org
From: @nopatience
https://swecyb.com/@nopatience/114009822145442393
In conversation about 9 days ago from infosec.exchange permalink
Attachments
1. Domain not in remote thumbnail source whitelist: telegram.org
  
  Telegram – a new era of messaging
  
  Fast. Secure. Powerful.
2. Untitled attachment
3. Untitled attachment
4. No result found on File_thumbnail lookup.
  
  Christoffer S. (@nopatience@swecyb.com)
  
  from Christoffer S.
  
  Netskope https://www.netskope.com/blog/telegram-abused-as-c2-channel-for-new-golang-backdoor Backdoor written in Golang using Telegram for C2-communication. Perhaps most interestingly the referenced Github repository with IoCs is not there anymore? Or will be published soon perhaps? #ThreatIntel #CyberSecurity

Feeds