Channel
@anyrun_app
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cite this entry
875subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002395012920 |
|---|---|
| Type | Channel |
| Username | @anyrun_app |
| Description | Empowering businesses with proactive security solutions: Interactive Sandbox, TI Lookup and TI Feeds. Official website: https://any.run | Sign up: https://app.any.run/?utm_source=telegram&utm_campaign=bio#register |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/anyrun_app |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 01:15 | 875 | no change |
| 7 Aug 2026, 17:15 | 875 | first reading |
19 posts held, back to 29 July 2026 — 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 pageof Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 19 (29 July 2026 – 7 August 2026) |
| Views total | 2,519 |
| Reactions total | 230 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 01:15 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
230 reactions across 19 posts, in 10 distinct kinds. The most used accounts for 50.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 116 | 50.4% | |
| 🔥 | 54 | 23.5% | |
| 👍 | 27 | 11.7% | |
| 👏 | 10 | 4.35% | |
| 👾 | 9 | 3.91% | |
| 🤔 | 4 | 1.74% | |
| 👨💻 | 3 | 1.30% | |
| 😱 | 3 | 1.30% | |
| 💯 | 2 | 0.87% | |
| 🤯 | 2 | 0.87% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 19 of the 19 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 230reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 29 July 2026 to 7 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
💡 The more AI adoption grows in cybersecurity, the more valuable human analysts become. AI can handle alert volume, but not the adversarial challenge. Attackers can adapt their techniques to bypass AI-driven detection, making the remaining threats harder to identify❗️ That's why skilled analysts who validate and investigate alerts are becoming more important, not less. 📖 AI in cybersecurity, SOC future & #ANYRUN v…
❤4💯2🔥2
🚨 Kali365 leaves one of its most useful pivots inside the browser: the runtime JS configuration. #ANYRUN Sandbox reveals the decrypted code behind the SharePoint lure, showing how the page sets up the device-code flow, generates the user code, and communicates with backend session endpoints. This turns the rendered page into a stronger investigation lead: analysts can move beyond the visible lure to session logic, …
❤5😱3👍2
🏦 Financial institutions are the #1 target for ransomware, credential theft, and social engineering. A SOC at an investment bank prevented hundreds of attempts with #ANYRUN. 📈 See how to strengthen security for banks
❤6🔥5👍2
⚡ Threat hunting without query syntax. Describe the behavior in plain language, #ANYRUN TI Lookup returns risk scores, threat names, indicators, and sandbox session links. 🎁 Using TI Lookup in your workflow? Tell us how — take a short survey and get a reward Not in TI Lookup yet? Reveal the malware behind any IOC, hunt related infrastructure across 50M+ samples, and review the sandbox evidence that connects it all.…
❤8🔥5👏2
🚨 PhantomEnigma shows the difference between blocking today’s C2 and tracking the operation behind it. #ANYRUN analysts recovered a Node.js/Electron backdoor with /nbw/ beaconing, 180-second task checks, eval()-based JavaScript execution, EXE delivery, and login persistence — capabilities that can turn a clean-looking sample into longer access, follow-on payload delivery, and higher fraud or data-exposure risk ⚠️ 🔍…
❤9🔥4👍2
🌐 ChongLuaDao protects 200M people against scams. #ANYRUN helps their team complete threat validation fast and produce reports for international partners like Interpol. 👉 Check out their lessons for SOC teams wanting to scale their impact.
❤8👏3👍2
⚠️ Active in July 2026. Three PhaaS kits targeting US organizations right now. 🔹 Sneaky 2FA: AiTM kit intercepting M365 session cookies, with Cloudflare CAPTCHA blocking automated analysis. 🔹 EvilTokens: captures OAuth tokens after victims complete real MFA on Microsoft's own login page. 🔹 EvilProxy: reverse-proxy PhaaS intercepting credentials in real time, evades automated detection systems. 🔍 All three tracked…
❤7👾3🔥2
🚨 July’s major attacks put cloud accounts, financial activity, and sensitive data at risk. Attackers abused 20+ government portals, used fake AI summit invitations, and manipulated Microsoft device code flows across the US, Europe, Brazil, and beyond. 🔍 See how your team can detect and respond faster
❤8🔥4👾3
⚡ Faster response starts with faster triage. With #ANYRUN's Interactive Sandbox files and URLs detonate in seconds, Automated Interactivity handles evasive threats, and Tier 1 reports give a structured verdict ready to act on. 👉 See how it works
❤5🔥4👍2
Phishing activity in the past 7 days 🐟 Track latest phishing threats in TI Lookup #TopPhishingThreats
❤7👾3🤔2
🚨 PhantomEnigma hijacks .gov.br portals to deliver backdoors while bypassing SPF, DKIM, and DMARC. Companies it targets face banking fraud and persistent RMM access ⚠️ ➡️ Update your SOC defense with our actionable research
❤5👏2🔥2
🚨 Remember Lazarus APT's IT workers scheme? Last year, we showed how the operation looked from the inside. Now there’s more to the story 🔥 New details are coming in Part 2, first presented by Mauro Eldritch & Heiner García at DEF CON 34 on August 8. Don't miss it. Stay tuned 🚀
❤8🔥4🤯2
Showing the 12 most recent of 19 posts we hold for @anyrun_app. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
Where does context loss hurt your SOC the most?
Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 19 most recent posts we hold, published 29 July 2026 to 7 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Citation-graph rank — 133,687 of 1,336,469entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“ANY.RUN” (@anyrun_app), 875 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/anyrun_app.
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.