Telegram RegisterThe public register of Telegram

Channel

Orca Cyber Weapons

@OrcaCyberWeapons

On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Handles named that no longer answer · Cite this entry

1,289subscribers

+1 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001771348040
TypeChannel
Username@OrcaCyberWeapons
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live10 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/OrcaCyberWeapons

Growth

1,2881,2891,288.57 August 2026 — 1,288 subscribers8 August 2026 — 1,288 subscribers10 August 2026 — 1,289 subscribers7 August 202610 August 2026
3 measurements spanning 4 days, net +1. 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 1,288–1,289 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 22:471,289+1
8 Aug 2026, 00:041,288no change
7 Aug 2026, 00:021,288first reading

Engagement

16 posts held, back to 6 March 2026the 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 · 30 days
20.0%
avg views ÷ 1,289 subscribers
Avg views / post
258
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 16 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 1 August 2026
Posts held16 (6 March 20261 August 2026)
Views total258
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 00:02 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.

Reaction mix

86 reactions across 15 posts, in 7 distinct kinds. The most used accounts for 34.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥3034.9%
2933.7%
👍1820.9%
❤‍🔥44.65%
👏33.49%
😢11.16%
🥱11.16%

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 15 of the 16 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 86reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 16 most recent posts we hold, published 6 March 2026 to 1 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.

Telegram Stars

Stars received
4
across the posts below
Posts paid on
1
of 16 we hold a reading for · 6%
Most on one post
4
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @OrcaCyberWeapons. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 16 most recent posts we hold for this entry, published 6 March 2026 to 1 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

1 Aug 2026, 15:50 UTC258 viewsread 7 August 2026

Static Devirtualization of Tencent VM by @BackEngineerLab . Great read for anyone interested in VM-based obfuscation and devirtualization. https://back.engineering/blog/31/07/2026/

7 Jul 2026, 09:15 UTC667 views6 reactionsread 7 August 2026

Update - GitHub flagged the org, cfgrip is on GitLab now: https://gitlab.com/BinaryHardening/cfgrip Appreciate everyone reaching out. GitLab's been solid, built in CI, container registry, group profile already up. Same code, nothing's stalled.

5😢1

2 Jul 2026, 12:46 UTC799 views6 reactionsread 7 August 2026

Binary Hardening just put out cfgrip v1.0.0 - https://github.com/BinaryHardening/cfgrip It loads PE and ELF binaries (32 and 64-bit), disassembles everything with Capstone, traces through indirect calls via GOT lookups, jump tables, and backward register tracking, figures out function boundaries from entry points, exports, prolog signatures, exception tables and data section pointers. Outputs the whole control flow

🔥6

27 Jun 2026, 20:50 UTC843 views10 reactionsread 7 August 2026

A dive into the PE file format https://0xrick.github.io/win-internals/pe1/ https://0xrick.github.io/win-internals/pe2/ https://0xrick.github.io/win-internals/pe3/ https://0xrick.github.io/win-internals/pe4/ https://0xrick.github.io/win-internals/pe5/ https://0xrick.github.io/win-internals/pe6/ [Mastering PE Structure for Malware Analysis: A Layman’s Guide](https://tech-zealots.com/malware-analysis/pe-portable-execut

🔥7👍3

25 Jun 2026, 17:53 UTC≈1,910 views7 reactionsread 7 August 2026

We’re building a small community around binary security research, focused on things like: - Reverse Engineering - Binary Obfuscation / Deobfuscation - Exploit Development - Compiler / interpreters... - Malware Analysis - Binary Hardening research we also work on open source tools and experiments here: GitHub → BinaryHardening GitHub Discord → BinaryHardening Discord If low level stuff and weird binaries are ur thi

7

25 Jun 2026, 17:38 UTC≈1,640 views5 reactionsread 7 August 2026

Post-Build PE Obfuscation Obfusk8 includes a post-build script to further harden the compiled binary by removing forensic artifacts. * Script Location: `Obfusk8/Obfusk8/SCRIPTS/obfuscate_pe.ps1 at main · x86byte/Obfusk8` * What it does: 1. Strips the Rich Header — removes the MSVC build-environment fingerprint that reveals compiler version and toolchain details. 2. Spoofs the TimeDateStamp — replaces

🔥32

25 Jun 2026, 14:58 UTC580 views5 reactionsread 7 August 2026

Obfusk8 v1.5 released! Enhanced AES string obfuscation with improved decryption reliability and stronger PE obfuscation hardening. Smoother, more resilient code protection. https://github.com/x86byte/Obfusk8/releases/tag/v1.5

🔥41

29 May 2026, 14:34 UTC813 views2 reactionsread 7 August 2026

https://prime.platacard.mx/file-service/static/ That's the Banco Plata S3 bucket we dumped earlier (platform-file-service-manager-prod-public in us-west-2). It serves financial documents: quarterly risk reports, signed Docusign contracts, Fitch/Moody's credit ratings, loan contracts, investment agreements, privacy policies — 849 files (156.4 MB). Authored by jorge.delacabada and Carlos Gonzalez. @OrcaCyberWeapons

2

26 May 2026, 11:37 UTC863 views8 reactionsread 7 August 2026

sbox Compile-time AES string obfuscation for C++. No XOR. No delimiters. No plaintext in .rdata. https://github.com/x86byte/sbox

👍52🥱1

25 May 2026, 11:13 UTC756 views3 reactionsread 7 August 2026

sbox - delimiter-less string obfuscation powered by compile-time AES Plaintext literals are a signature. Standard string serialization using delimiters is easy to trace and trivial to reverse. I wrote sbox to handle both single-string and multi-string encryption at compile-time, ensuring that sensitive source data is never exposed in the constant pool. The project ports the AES8 core from Obfusk8 to the NeetCode "E

2👍1

16 Mar 2026, 01:41 UTC≈1,130 views8 reactionsread 7 August 2026

RE//verse 2026: Deobfuscation of a Real World Binary Obfuscator by James McGowan and Bas Zweers @OrcaCyberWeapons

🔥5👍3

14 Mar 2026, 12:11 UTC≈1,000 views6 reactionsread 7 August 2026
Photo

ent8 Bin2bin Obfuscator answers about the @PELock question "but the question is - can it obfuscate ntoskrnl.exe"

3🔥2👏1

Showing the 12 most recent of 16 posts we hold for @OrcaCyberWeapons. 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.

Citation-graph rank

Citation-graph rank — 285,919 of 1,160,990entries 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

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.

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 10 August 2026 — this entry's latest reading, not the date you are reading this.

“Orca Cyber Weapons” (@OrcaCyberWeapons), 1,289 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/OrcaCyberWeapons.

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.