Telegram RegisterThe public register of Telegram
Telegram profile photo for IoT/ICS Security & Malware

Channel

IoT/ICS Security & Malware

@IotPenetrationTesting

On this record: Growth · Engagement · Posts · Citations · Cite this entry

614subscribers

+8 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001255799940
TypeChannel
Username@IotPenetrationTesting
CreatedBetween 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live3 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 3 September 2026
On Telegramt.me/IotPenetrationTesting

Growth

6066146107 August 2026 — 606 subscribers7 August 2026 — 606 subscribers21 August 2026 — 610 subscribers27 August 2026 — 612 subscribers3 September 2026 — 614 subscribers7 August 20263 September 2026
5 measurements spanning 28 days, net +8. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 605–615 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Sept 2026, 23:16614+2
27 Aug 2026, 10:57612+2
21 Aug 2026, 09:59610+4
7 Aug 2026, 07:46606no change
7 Aug 2026, 07:36606first reading

Engagement

20 posts held, back to 16 October 2022the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 9 June 2023. An engagement rate over an empty window would be a number about nothing.

Recent posts

9 Jun 2023, 11:08 UTC≈1,450 viewsread 7 August 2026

درود بدلیل مشغله کاری از تمامی دوستان فعال در حوزه های سایبری دعوت میشود به آیدی زیر پیام داده و در صورت تایید به عنوان مدیر و ویراستار جدید کانال انتخاب شوند @Offensive01Bot

18 Apr 2023, 08:53 UTC≈1,870 viewsread 7 August 2026

​​IoT-PT A Virtual environment for Pentesting IoT Devices https://github.com/IoT-PTv/IoT-PT Persian : یک محیط مجازی برای Pentesting دستگاه های IoT https://github.com/IoT-PTv/IoT-PT #IoT @Iotpenetrationtesting

18 Apr 2023, 08:17 UTC≈1,380 viewsread 7 August 2026

​​IoTSecurity101 A Curated list of #IoT Security Resources https://github.com/V33RU/IoTSecurity101 @Iotpenetrationtesting

17 Apr 2023, 11:11 UTC≈1,180 viewsread 7 August 2026

A tool which utilizes Shodan to detect vulnerable IoT devices. BAMF is an open-source tool designed to leverage Shodan (a search engine for the Internet of Things) to discover routers vulnerable to CVE-2013-6026, commonly known as Joel's Backdoor, a severe vulnerability allowing unauthenticated access to the administration panel of many routers made by D-Link, one of the world's largest manufacturers of routers for

16 Apr 2023, 07:21 UTC≈1,040 viewsread 7 August 2026

​​awesome-iot-hacks A Collection of Hacks in IoT Space so that we can address them (hopefully). https://github.com/nebgnahz/awesome-iot-hacks #IoT @Iotpenetrationtesting

11 Apr 2023, 07:57 UTC≈1,000 viewsread 7 August 2026
File

A Detailed Analysis of the Gafgyt Malware Targeting IoT Devices , 2022. #Malware_analysis #IoT_Security @Iotpenetrationtesting

11 Apr 2023, 07:52 UTC921 viewsread 7 August 2026
File

"ShellCore: Automating Malicious IoT Software Detection by Using Shell Commands Representation", 2021. #IoT_Security @Iotpenetrationtesting

21 Feb 2023, 15:08 UTC≈1,400 viewsread 7 August 2026

🔥🔥🔥Xiongmai IoT Exploitation(exploited in the wild) There are a number of reasons Xiongmai devices are interesting targets: 💾 The first reason is there are a lot of them on the internet(around 200,000). 💾The second reason is these devices have been affected by a handful of high or critical vulnerabilities(CVE-2017-7577, CVE-2018-10088, CVE-2020-22253, CVE-2021-41506, CVE-2022-26259, CVE-2022-45045 & CVE-2022-45640)

9 Feb 2023, 03:47 UTC≈1,200 viewsread 7 August 2026

+ A Collection for IoT Security Resources https://github.com/V33RU/IoTSecurity101#Books-For-IoT-Pentesting + A Virtual environment for Pentesting IoT Devices https://github.com/IoT-PTv/IoT-PT #IoT #Pentest @Iotpenetrationtesting

7 Feb 2023, 16:08 UTC≈1,060 viewsread 7 August 2026

To some admins to post IoT & ICS Hacking posts on the channel to share with other friends and if possible to offer conferences. Contact : @NetPwn

2 Feb 2023, 08:03 UTC≈1,160 viewsread 7 August 2026
File

IoT Security Checklist The checklist lists 39 essential security functions that enable IoT devices to be operated safely even in an environment where threats exist, along with background information on why they are necessary IoT Security Checklist Diagram, Users Manual, Checklist in .xlsx: https://www.jpcert.or.jp/english/pub/sr/IoT-SecurityCheckList.html #IoT @Iotpenetrationtesting

Showing the 12 most recent of 20 posts we hold for @IotPenetrationTesting. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Mentions

Names

Channels on the register whose handles appear in this channel's posts.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 3 September 2026 — this entry's latest reading, not the date you are reading this.

“IoT/ICS Security & Malware” (@IotPenetrationTesting), 614 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/IotPenetrationTesting.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.