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/

Channel
Orca Cyber Weapons
@OrcaCyberWeapons
On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Handles named that no longer answer · Cite this entry
1,309subscribers
+21 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 |
|---|---|
| Type | Channel |
| Username | @OrcaCyberWeapons |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 4 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 4 September 2026 |
| On Telegram | t.me/OrcaCyberWeapons |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Sept 2026, 22:36 | 1,309 | -2 |
| 1 Sept 2026, 14:05 | 1,311 | -2 |
| 29 Aug 2026, 22:34 | 1,313 | +1 |
| 26 Aug 2026, 14:17 | 1,312 | +5 |
| 23 Aug 2026, 11:58 | 1,307 | +8 |
| 20 Aug 2026, 05:08 | 1,299 | +4 |
| 17 Aug 2026, 10:05 | 1,295 | +3 |
| 13 Aug 2026, 18:25 | 1,292 | +3 |
| 10 Aug 2026, 22:47 | 1,289 | +1 |
| 8 Aug 2026, 00:04 | 1,288 | no change |
| 7 Aug 2026, 00:02 | 1,288 | first reading |
Engagement
16 posts held, back to 6 March 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 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 16 posts for this entry, the most recent from 1 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
86 reactions across 15 posts, in 7 distinct kinds. The most used accounts for 34.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 30 | 34.9% | |
| ❤ | 29 | 33.7% | |
| 👍 | 18 | 20.9% | |
| ❤🔥 | 4 | 4.65% | |
| 👏 | 3 | 3.49% | |
| 😢 | 1 | 1.16% | |
| 🥱 | 1 | 1.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 86 reactions 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
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
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
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
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
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 …
🔥3❤2
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
🔥4❤1
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
sbox Compile-time AES string obfuscation for C++. No XOR. No delimiters. No plaintext in .rdata. https://github.com/x86byte/sbox
👍5❤2🥱1
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
RE//verse 2026: Deobfuscation of a Real World Binary Obfuscator by James McGowan and Bas Zweers @OrcaCyberWeapons
🔥5👍3
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.
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.
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@OrcaCyberWeapons named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 8 August 2026 – 8 August 2026
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 4 September 2026 — this entry's latest reading, not the date you are reading this.
“Orca Cyber Weapons” (@OrcaCyberWeapons), 1,309 subscribers as measured 4 September 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.