Channel
@sharedlicense
On this record: Topic · Growth · Engagement · Posts · Cite this entry
1,069subscribers
+9 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001158074939 |
|---|---|
| Type | Channel |
| Username | @sharedlicense |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 1 November 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 1 November 2026 |
| On Telegram | t.me/sharedlicense |
Software piracy — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 19 September 2026 and assigned it the closest of 31 fixed categories, at 54% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Nov 2026, 20:06 | 1,069 | +3 |
| 27 Oct 2026, 08:36 | 1,066 | -1 |
| 24 Oct 2026, 07:00 | 1,067 | +4 |
| 14 Oct 2026, 09:31 | 1,063 | +2 |
| 10 Oct 2026, 18:38 | 1,061 | -1 |
| 5 Oct 2026, 00:56 | 1,062 | +2 |
| 25 Sept 2026, 15:16 | 1,060 | -2 |
| 16 Sept 2026, 22:21 | 1,062 | +3 |
| 8 Sept 2026, 15:41 | 1,059 | -2 |
| 27 Aug 2026, 12:34 | 1,061 | +2 |
| 24 Aug 2026, 21:08 | 1,059 | +2 |
| 17 Aug 2026, 19:43 | 1,057 | +2 |
| 14 Aug 2026, 14:13 | 1,055 | -3 |
| 11 Aug 2026, 09:44 | 1,058 | -2 |
| 8 Aug 2026, 00:18 | 1,060 | no change |
| 7 Aug 2026, 23:29 | 1,060 | first reading |
20 posts held, back to 27 December 2025 — the 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 31 July 2026. An engagement rate over an empty window would be a number about nothing.
📢 Announcement: DirectAdmin Update v1.705 DirectAdmin has been updated to the latest stable version. If you need to force the update manually on your server, run the following command: /usr/bin/update_diradm --force If you encounter any issues after the update, please open a support ticket. ➖➖➖➖➖➖➖➖➖➖➖➖ SLC Software - SharedLicense SharedLicense [email protected]
📢 Crypto Payment Gateway Notice Dear Customers, Please note that our previous cryptocurrency wallet addresses have expired and should no longer be used for new payments. A new crypto payment gateway is now active. ⚠️ Important: For all future deposits, please use the new wallet addresses displayed during the payment process. Do not send funds to any wallet addresses you may have used previously. We currently supp…
🚨 Urgent Security Notice – LiteSpeed cPanel Plugin (Jun 14, 2026) LiteSpeed has disclosed a critical privilege escalation vulnerability (CVE-2026-54420) affecting the LiteSpeed User-End cPanel Plugin versions prior to v2.4.8. The vulnerability is reportedly being actively exploited. If you are using LiteSpeed with cPanel, please update immediately to: ✅ LiteSpeed WHM Plugin v5.3.2.1 or later ✅ LiteSpeed cPanel Plu…
🚨 Important Security Alert – cPanel & LiteSpeed (May 19, 2026) A critical vulnerability was found in the LiteSpeed cPanel plugin that may allow unauthorized ROOT access. ✅ cPanel now automatically removes the LiteSpeed WHM plugin during updates. 📌 LiteSpeed Web Server itself continues working normally. 🔧 Run update immediately: /scripts/upcp --force 🔧 Remove LiteSpeed plugin manually now: usr/local/lsws/admin/m…
🚨 cPanel Released Another Security Update The cPanel Change Log now includes a new Targeted Security Release containing important security fixes and system improvements for WHM/cPanel servers. You can also monitor all official security advisories and announcements here: 🔐 cPanel Security Advisories Please update your server immediately using: /usr/local/cpanel/scripts/upcp --force ⚠️ Delaying critical security …
🚨 Important WHMCS Security Update – CVE-2026-29204 A critical security vulnerability has been identified in WHMCS versions 7.4 and later. This issue could allow an authenticated user to access or perform actions on services belonging to other users due to insufficient authorization checks within the Client Area. ✅ Affected Versions: • All WHMCS 9.x builds prior to 9.0.4 • All WHMCS 8.x builds prior to 8.13.3 • All…
⚠️ Security Update Recommended The following security vulnerabilities have been patched: • CVE-2026-29201 — Arbitrary file read • CVE-2026-29202 — Perl code injection • CVE-2026-29203 — Symlink privilege escalation issue Please update your server immediately using: /usr/local/cpanel/scripts/upcp --force Updating is strongly recommended for all servers. @SharedLicense
⚠️ A newly disclosed Linux kernel vulnerability known as Dirty Frag has been identified and may affect shared hosting environments. Our team is currently reviewing the impact and preparing patched kernel updates. We will publish an additional announcement once fixed kernels are available in the repositories. Until the official patches are released, we recommend applying the temporary mitigation steps provided here:…
CloudLinux users can update their Apache using cl-ea4-testing repo, https://cloudlinux.zendesk.com/hc/en-us/articles/27239221402908-Apache-CVE-2026-23918-ea-apache24-2-4-67-is-not-available-in-CloudLinux-repositories Command : yum update ea-apache24 --enablerepo=cl-ea4-testing
🛡 Mitigations – CVE-2026-23918 (Apache RCE) Due to Apache’s wide usage, this vulnerability is high-risk and needs immediate attention. ⚠️ If you can’t update immediately, take these actions: • 🔄 Upgrade to Apache 2.4.67 → Only full fix for all vulnerabilities • 🚫 Disable HTTP/2 (temporary) → Reduces exposure to RCE attack • 🧩 Remove mod_dav_lock (if unused) → Mitigates CVE-2026-29169 • 🔐 Audit .htaccess permissions →…
🚨 Important Security Update – Apache HTTP Server A critical vulnerability (CVE-2026-23918) has been identified in Apache’s HTTP/2 module, which could potentially be exploited for remote code execution. 🔗 More details: https://support.cpanel.net/hc/en-us/articles/40229402602519-Security-CVE-2026-23918 ⚠️ Action required: Update your Apache immediately. 🖥 RHEL-based servers yum clean all yum makecache yum -y update e…
🚨 Security Update – cPanel / WHM cPanel has just released another update to address recent security issues. Latest versions: 124.0.34 110.0.112 118.0.64 126.0.56 132.0.29 134.0.23 136.0.7 ⚠️ Make sure to update all your cPanel servers again: /scripts/upcp --force Run it manually if auto-updates are disabled or your version is locked.
Showing the 12 most recent of 20 posts we hold for @sharedlicense. 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.
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 1 November 2026 — this entry's latest reading, not the date you are reading this.
“SharedLicense” (@sharedlicense), 1,069 subscribers as measured 1 November 2026. Telegram Register, tgregister.com/channel/sharedlicense.
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.