# Others built a knife for "taking apart any software"; he built a shield: how BLA borrowed from REA, which has 430k stars, and got 2000 stars in one week · GitHub open-source project

> Source: https://stringers.io/en/github/gh_qybaihe__bla.html (Stringers / 什么值得做, generated 2026-11-08)
> Stringers answers one question every day: what small product can one or two people build in a few months and actually make money from. Numbers come from 15 databases we collect daily, each with source and date.
> For agents: these verdicts and the underlying databases (verified revenue, App Store / Google Play charts, ad libraries, GitHub, Product Hunt…) are queryable live over MCP — tools today / hot / products / directions / direction / data. Setup: https://github.com/komako-workshop/stringers (the user logs in at stringers.io → "配置 agent" to get a personal URL). Site index: https://stringers.io/llms.txt

> REA climbed to hundreds of thousands of stars, spreading the anxiety that "my app can be copied by AI in minutes". Dozens of companion repos were teaching people to use it, and the defensive side had only this one. The name, slogan, and one-command usage were all aimed at REA. The author first self-promoted on linux.do, then security X accounts and Weibo reshared it, and 10-31 gained 738 stars in a single day.

[GitHub open-source project](https://stringers.io/en/github/index.md) · written 11-6

qybaihe/bla · qybaihe

# Others built a knife for "taking apart any software"; he built a shield: how BLA borrowed from REA, which has 430k stars, and got 2000 stars in one week

**What it is** An open-source anti-AI reverse-engineering tool: it plants decoys and noise in the programs you're about to ship, so AI reverse-engineering agents like REA read wrong, loop, and burn their budget, while the program still runs normally.

**Why it took off** REA grew to several hundred thousand stars and brought with it an anxiety that "my app can be copied by AI in minutes." Dozens of satellite repos teach people to use it, and only this one addresses the defensive side. The name, the slogan, and the one-line command are all aimed at REA. The author first self-promoted on linux.do, then security-circle accounts on X and Weibo reposted it, and it gained 10-31 stars in 738 day.

**C** **How you could follow it** Don't build another anti-REA tool. Watch for the next fastest-growing hit and, within a week or two of its appearance, build its counterpart or companion, as complete and easy to use as the original. Or build a neutral attack-and-defense evaluation bench that BLA didn't build.

Grade C: the anti-REA position is winner-take-all. The earlier antirea and DeRea, and reashield, which came 6 days later, each have only a few to a few dozen stars, so following now won't get traction. The realistic lesson, building a counterpart to a hit, requires betting on the next hit and getting there within one to two weeks, and its effectiveness is tied to REA's version and could stop working at any time. Spreading within small circles

Data (updated daily) · Repo created 2026-10-25 · 2,724 stars · 7 days +1,027

GitHub · stars

Data 2026-10-28 → 2026-11-08 (12 days, 12 observations). Points before 10-28 come from deeply / archive backfill, not every day has one

BLA (Blind LLM Agents) is an open-source "anti-AI reverse engineering" tool. It plants decoys and noise in the programs you're about to ship, so AI reverse-engineering agents like REA misread them, loop, and burn through their budget, while the program itself runs as normal. The author is an undergrad with 71 followers. The project was created in Oct 25, and by Nov it had 6 2,425 stars. Almost all of those stars are borrowed: borrowed from REA's fame and from the anxiety REA stirred up. Below: what it is, why this one took off, why the copycats didn't get traction, and what you can take from it.

### An indie dev who got copied

On the evening of Oct 2026 27, GitHub user qybaihe (Timo Zhang) posted on linux.do under the "open-source promotion" tag, titled "REA is everywhere. As an indie dev, my answer is to confuse it!" The first line of the post:

> Ever since my app's features got copied and rebuilt in a few minutes, I've been thinking about how to hit back.

He went on to describe the idea: "poison" the binary so REA gets wrong information; generate piles of look-alike functions to waste the attacker's tokens until they hit their budget and stop; for closed-source commercial models, slip in realistic-looking fake keys to trigger the model's own safety refusals; or inject fake system errors to lure the AI into chasing environment problems. He said the project was "built by opus and argon following this approach," and the name is a deliberate counter: "re is red, so bl is blue."

Replies included "Anti-AI anti-reversing? Might be a real market," "Definitely, and probably a big one," "Seriously bookmarked, starred, forked, the full combo," and a skeptic: "In the end this war is just left foot stepping on right foot; it comes down to whose model is stronger" (linux.do, 10-27).

That day the repo had roughly a hundred-plus stars. By Oct 31, it was gaining 738 stars a day.

### What it is

An npm package `bla-agents`, MIT licensed, both an MCP server and an agent skill. Usage mirrors REA: a single `npx bla-agents harden .`, or tell Claude Code, Cursor, or Codex "Harden my software against REA."

It targets what you're about to ship: JS bundle outputs, Electron asar, WebAssembly, SQLite, model files, plus over a dozen other formats including Go, BEAM, and EVM. Unlike traditional obfuscation (javascript-obfuscator and the like, which aims to make code unreadable to humans), its target is the weaknesses of LLM agents: limited context and budget, a tendency to trust decompiled output, and safety refusals triggered by sensitive-looking content. The README includes a per-format table of tests run against real REA, showing which REA resource limit each format hits (for example, an ASAR header at 16 MiB, or GGUF nested 32 levels). Items that are estimates and unverified are marked separately. The slogan is three words: Poison → Exhaust → Hallucinate.

### First, REA: a knife, and the anxiety it brought

`morluto/rea` (Reverse Engineer Anything) is an MCP tool that lets agents take apart binaries, JS/Electron apps, .NET, and websites, then rebuild their features. The repo was created in April, then blew up in October: 10-09 37k stars, 10-16 281k, 11-06 434k (GitHub daily star count). Scientific American interviewed the author, and YouTube had tutorials promising to "clone any software in minutes." In Nov 2, Tom's Hardware and TechPowerUp reported that Anthropic had begun refusing game-cloning and reverse-engineering requests in Claude Code. "AI copying products" had become a public topic.

A ring of repos riding REA's coattails appeared fast: leanrea with 4,036 stars, REA-Prompts 3,693, rea-video 2,648, Awesome-REA 1,057... nearly all were "how to use REA." The only one on the defensive side that gained real traction was BLA.

### Where the stars came from: Chinese community ignition, security circles relaying

| Date | What happened | Daily stars around launch |
|---|---|---|
| 10-25 | Repo created, published to npm (271 downloads that day), site bla.tools went live, README opens in 22 languages | Starting point |
| 10-27 | Author self-promoted on linux.do (the post above) | — |
| 10-29 | Security X accounts @0x0SojalSec and @blackorbird reposted: "You've seen REA tear apps apart... Someone built the defense" | 202 |
| 10-30 | Sina / Weibo posts "a shield that adds layers against AI disassembly"; red-team account @ipurple and Chinese account @NFT_Chen reposted; Gulu Ji wrote "Today's hottest GitHub project lets agents reverse engineer any software; the same day, someone released a shield specifically against it" | 600(+398) |
| 10-31 | Ranked 15 on Trendshift that day, followed by a batch of AI news aggregators; npm downloads hit 1,028 that day | 1,338(+738) |
| 11-01 to 11-06 | LinkedIn post; reamcp.dev listed it as a "defensive use case" for REA; added to the Awesome REA list. The author shipped to v3.0 within two weeks, and external contributors submitted over a dozen PRs in a single day | Daily +80 to +190,11-06 to 2,425 |

Star counts come from GitHub's daily records; npm downloads come from npm's official stats (including CI and mirrors, so not equal to real users). I found no evidence of a Hacker News or Product Hunt launch, nor of paid acquisition or star-buying. Forks: 317, which is 13% of stars, is high. This may relate to the Chinese community habit of "star, fork, the full combo" and to people who genuinely wanted to modify it (inference).

Every reposted headline followed the same structure: "You've seen REA tear apps apart. Someone built the defense." In other words, everyone writing about REA had a reason to mention BLA in passing.

### Why this one and not the earlier ones

BLA wasn't the first anti-REA project. Others came before and after, but all stalled at a few dozen stars:

| Project | Repo created | star | How BLA differs |
|---|---|---|---|
| kriszwart/diarea | 10-12 | 81 | Helps you check frontend-leaked keys and source maps. It's an audit tool, not hardening. |
| MockirDev/antirea | 10-21 | 36 | Mainly injects instructions for agents into a project. No test table, no one-command MCP. |
| zhcalvin/DeRea | 10-22 | 45 | Simple packaging, few formats |
| yaklang/DropYourGunKid | 10-23 | 52 | Defends against websites being scanned by AI security agents, not against shipped artifacts being taken apart |
| HMAKT99/reashield | 10-31 | 2 (npm weekly downloads 904) | JS only. The author pushed a long dev.to article, but stars never took off. |

Per GitHub, 11-06. Comparing, BLA won on three things, none of them a technical barrier:

1. **Name and slogan directly answer REA** . BLA is "Make reverse engineering bankrupt again," a riff on REA, and the README's first line defines it as "Counter-REA."

2. **Looks just like REA** . MCP + skill + one npx line. Users think "use BLA the way you use REA," with zero learning cost.

3. **Gives people material to share** . Tables that separate tested from estimated results (the Sina post and a later fact-check article both specifically praised this), before-and-after comparison images for "unhardened vs hardened" disassembly, a README in 22 languages, and three memorable words. Security accounts were willing to repost because there was something to repost.

Timing mattered too. When BLA launched, REA was already at 380k stars and still gaining 5,000+ a day. Discussion was at its peak, while the defensive side was empty. antirea, which launched 4 days earlier, wasn't finished, and reashield, 6 days later, arrived after the slot was taken.

Its weaknesses are also clear. Someone on X pointed out this is still the packer arms race: once agents get debuggers and bigger budgets, the margin shrinks fast. Others said it's just obfuscation with a new target. BLA's tests were run against REA's current resource limits, so if REA changes one parameter, part of the "tested" results stop holding. The real protective effect has only been reproduced by the author, and "wastes 612x the tokens" is an estimate.

### If it were you

**In one sentence** : building another anti-REA tool is already late. What's worth taking is the playbook: **once a repo explodes to hundreds of thousands of stars, build its counterpart or companion,** and make it as complete and as easy to adopt as the original. Whether this can work again depends on whether you can ship within a week or two after the next hit appears.

**Who it's for** : developers who build dev tools and move fast, who can deliver "an npm package + MCP + one command + a solid README" in one to two weeks, and who watch GitHub trending and can judge what side effects a hit creates. No following needed. BLA's author has 71 followers.

**Who it's not for** : people hoping to carve out a slice of the anti-REA space (reashield came 6 days later with a long article, and 11-06 has only 2 stars); people building a long-term security product that has to hold up to expert scrutiny, since projects that "target one specific tool" tie their effectiveness to that tool's version; and people who only write code and won't go out and tell the story in communities.

**How to do it** , from most to least reliable:

1. **Be the counterpart to the next hit** : watch the fastest-rising repos and ask "who does this scare, and who does it hurt?" Dozens of repos orbit REA, 99% of them teaching people how to use it. The defensive side had one slot, and BLA took it. When the next frightening agent tool appears (scrapers, automated order-spamming, bulk site cloning, and so on), the same empty slot will open up again.

2. **Fill the gap BLA left** : BLA's weakest point right now is whether its effectiveness has been independently verified. A neutral "AI reverse-engineering attack/defense benchmark" that runs REA and other open-source reverse agents against different hardening schemes with standard tests and public leaderboards would draw people from both offense and defense, and wouldn't break just because REA changes a parameter. This is an inferred gap; I didn't find an existing project.

3. **Copy the packaging** : even if you don't build a counterpart, BLA's README craft is worth copying: tested vs estimated results kept separate, comparison images, multiple languages, one command, and a line you can say directly to an agent.

**How to get users** : follow BLA's order. First, self-promote on linux.do with the "open-source promotion" tag, and open with a personal story ("my app got copied in a few minutes" spreads far better than describing features), to collect the first stars and feedback. Then write the headline as "You've seen what X did. Someone built a counter," and find accounts in that circle to repost it. Finally, submit PRs to the hit's Awesome lists and use-case sites, so every article about the hit mentions you along the way.

**When to move** : for a counterpart position, the window is one to two weeks after the hit appears. BLA launched more than two weeks after REA's explosion, when REA was still gaining 5,000 stars a day. If you wait until the hit's momentum fades, fewer people are writing about it, and fewer will write about you.

**Signs you misjudged** : (1) BLA's daily stars drop to single digits within a month and npm downloads fall with them, which would mean the counterpart only captures the hit's hottest two weeks and the long tail is thin; (2) REA changes its resource limits or learns to spot decoys, BLA's test table breaks widely, and its stars keep rising, which would mean people are starring the narrative, not the effect, so the benchmark route wouldn't work; (3) conversely, after the next hit, someone uses this playbook to get a thousand stars within two weeks, which would mean the playbook is replicable and you should move even earlier next time.

---

Data and sources: GitHub repos qybaihe/bla and morluto/rea (pages, README, Releases, issues) (11-06); GitHub daily star counts (10-09 to 11-06); npm official download stats (10-25 to 11-05); author self-promo post on linux.do (10-27); original posts from X accounts @0x0SojalSec, @blackorbird (10-29), @ipurple, @NFT_Chen (10-30); Sina (10-30), Gulu Ji (10-30), LinkedIn (11-01), explainx.ai (11-03), dev.to (11-01), Trendshift, reamcp.dev; Tom's Hardware / TechPowerUp (11-02). Real user numbers can't be inferred from download counts. How many stars each repost brought in can't be determined. The reason for the high fork rate is inference.

[GitHub repo ↗](https://github.com/qybaihe/bla)

**Research notes: competitor table, acquisition evidence, full research report**

Competitors

| Name | Where | Launched | Scale | How it differs from this one |
|---|---|---|---|---|
| MockirDev/antirea | Open source | 2026-10-21 | 36 stars | Mainly injects instructions for agents and terminal shims into a project. No REA-specific tests, no one-command MCP, no multilingual README. |
| zhcalvin/DeRea | Open source | 2026-10-22 | 45 stars | Simple packaging, doesn't cover many formats, and has no tests. |
| yaklang/DropYourGunKid (DYGK) | Open source | 2026-10-23 | 52 stars | Defends against websites being scanned by AI security agents, not against shipped artifacts being taken apart |
| kriszwart/diarea | Open source | 2026-10-12 | 81 stars | Checks frontend leaks. It's an audit tool, not hardening. |
| HMAKT99/reashield | Open source | 2026-10-31 | 2 stars, npm weekly downloads 904 | JS only, launched 6 days later, relied on dev.to content promotion |
| javascript-obfuscator | Open source | 2016 | 16322 stars | Traditional obfuscation guards against humans; BLA targets LLM agents' budgets and context |
| Jscrambler / VMProtect / Themida / PyArmor | Other | Years ago | Mature commercial product (scale not verified) | Paid packers, virtualization, encryption; BLA is free, doesn't change the format, and works with one npx command |
| Anthropic refuses reverse-engineering requests in Claude Code | Big-company features | 2026-11 first | Covers all Claude users | Blocking on the model side gets bypassed by switching to an open-source model; BLA is a layer the publisher controls |

Where users come from

- **Verified** **Riding the hit's name (positioned as REA's counterpart)** : the name BLA is a counter to REA; the README's first line is Counter-REA; repost threads read "You've seen REA tear apps apart, someone built the defense"; reamcp.dev lists it as an REA defense use case and it's in the Awesome REA list

- **Verified** **Self-promotion by the author on linux.do** : 10-27 "[Open-source promo] REA is everywhere; as an indie dev, my answer is to confuse it!", telling the story of their app being copied

- **Verified** **Reposts from X security accounts and Chinese accounts** : @0x0SojalSec 10-29, @blackorbird 10-29, @ipurple 10-30, @NFT_Chen 10-30, followed by 10-30 +398, 10-31 +738 stars

- **Verified** **Weibo / Sina, Chinese AI communities** : a Sina post 10-30 09:49 "adding an anti-AI-decompilation shield to binaries"; Guluji 10-30 "attack and defense in the same week"

- **Verified** **GitHub Trending / Trendshift and AI aggregator sites** : #15 on Trendshift's daily chart; listed by Kitploit, The Daily Commit, offsecblog, explainx and others 10-30~11-03

- Inferred **Reddit r/gamedev** : a search result shows a thread "For those scared of REA and getting cloned (BLA)"; the body is not visible 403

- **Verified** **README craftsmanship (22 languages, comparison charts, benchmark tables)** : the repo README

## Why qybaihe/bla (BLA, Blind LLM Agents) took off

> In one line: BLA is an open-source "anti-AI-reverse-engineering" hardening tool (npm `bla-agents`, MIT). It "poisons, exhausts, and hallucinates" the artifacts you ship (JS / Electron asar / WASM / SQLite / model files / Go / BEAM / EVM), so AI reverse-engineering agents like REA hit resource limits, chase decoys, and burn through tokens, while the program's runtime results stay unchanged. Verdict: **it is one of the fastest-growing repos in history, and the counterpart to REA (Reverse Engineer Anything, 430k stars)** . Three weeks after REA exploded, it was almost the only serious "shield" on the internet. It mirrored REA's naming, slogans, and delivery format (MCP + skill + one command), then ignited with self-promotion in Chinese communities and reposts from security accounts on X, reaching about 2000 stars in a week. The differentiation is mainly positioning and narrative, not technical barriers.

### 1. Basic data

| Project | Value | Source |
|---|---|---|
| Repo created | 2026-10-25 | GitHub API |
| star / fork | 2425 / 317 (library 11-06); 2505 / 331 (GitHub API 11-06 14:40 UTC) | github repo_day table; GitHub API |
| Daily stars | 10-28 167 → 10-29 202 → 10-30 600(+398)→ **10-31 1338(+738)** → 11-01 1697 → 11-02 1811 → 11-03 1974 → 11-04 2056 → 11-05 2237 → 11-06 2425 | github repo_day |
| npm downloads | 10-25 271, 10-29 95, 10-30 169, **10-31 1028** , 11-01 524 … 11-05 585; about 2949 weekly downloads, about 3294 monthly | npm registry / api.npmjs.org (includes CI and mirrors, so not equal to real users) |
| Charts | Trendshift "#15 Repository Of The Day" (README badge, [trendshift.io/repositories/323569](https://trendshift.io/repositories/323569)) | Repo README |
| Author | Timo Zhang (qybaihe), undergraduate, bio reads "3 AI hackathon wins in half a year, over $20k in prize money"; LobeHub contributor; 71 GitHub followers; predecessor `mu` has 576 stars | GitHub API |
| Pattern | Shipped to v3.0.0 within two weeks; 11-05 to 11-06 external contributor DeryFerd opened 10+ PRs in a single day (CI, CSP, manifest signing) | GitHub Releases / Issues |

The author had no audience to start with (71 followers, predecessor 576 stars), so the traffic was not built-in; it was borrowed.

### 2. Background: what REA is and how big it got

- `morluto/rea`: "Reverse engineer anything with agents", an MCP service + CLI that lets agents like Claude Code and Codex take apart binaries, JS / Electron, .NET, and websites, then replicate their functionality. Created 2026-04-14, exploded in October: 10-09 37k stars → 10-13 183k → 10-16 281k → 11-06 434k (GitHub repo_day), forks 108k.

- Massive media coverage: Scientific American interviewed the author (HN 2026-10-30), Miles Deutscher posted a long X tutorial, a YouTube video "How To Use REA To Clone Any Software In Minutes", plus dev.to, Medium, Reddit r/tech_x and more (Jina search).

- It spawned a crowd of name-riding spinoffs: leanrea 4036 stars, REA-Prompts 3693, rea-video 2648, open-claude-ui 1715, Awesome-REA 1057 and others (GitHub repo_profile / GitHub search). **Almost all were attackers or "what to do with REA" projects; BLA was the only defense-side entrant.**

- Platform event: 2026-11-02 Tom's Hardware / TechPowerUp reported that Anthropic restricted Claude Code from game cloning and reverse-engineering requests (hackernews library). It shows "AI copying products" is now a public issue, and big vendors are starting to tighten from the model side.

**Why users showed up now** : REA made indie developers genuinely afraid that "an agent can take apart and clone my app in minutes" for the first time. The BLA author's self-promo post on linux.do opens with "Ever since my app's features were copied in a few shots, I've been thinking about how to hit back." That anxiety was built by REA's hundreds of thousands of stars, and BLA caught it.

### 3. Competitors

| Name | Where | When | Scale | How BLA differs |
|---|---|---|---|---|
| MockirDev/antirea | Open source | 2026-10-21 (4 days before BLA) | 36 stars | Took the "agent instruction barrier + terminal shim + build hardening" route, mainly stuffing instructions meant for agents into the project; no benchmark table measuring REA's resource limits, no one-command MCP setup, no multi-language README |
| zhcalvin/DeRea | Open source | 2026-10-22 | 45 stars | "Anti Rea", with a very simple description and packaging |
| yaklang/DropYourGunKid(DYGK) | Open source | 2026-10-23 | 52 stars | Web deception / honeypots against AI security-scanning agents; protects websites from being scanned, not shipped artifacts from being decompiled |
| kriszwart/diarea | Open source | 2026-10-12 | 81 stars | Defender-side "self-audit" tool: finds leaked keys, source maps, and API maps in frontends; it's an audit, not hardening |
| HMAKT99/reashield | Open source + npm | 2026-10-31 (6 days after BLA) | 2 stars, npm weekly downloads 904 (10-30~11-05) | JS only: computed-expression imports, runtime IPC names, decoys; promoted with a dev.to long post "so I built the REAshield". See "Copycats" below |
| javascript-obfuscator | Open source | 2016 | 16322 stars (github library) | Traditional obfuscation targets humans and deobfuscators; BLA targets the LLM agent's context and budget. The opposite direction exists too: humanify (3296 stars, uses an LLM to deobfuscate), which shows traditional obfuscation can't stop LLMs |
| Jscrambler, VMProtect / Themida, PyArmor, bytenode, Electron asar encryption | Commercial / other | Years | Mature commercial product (scale not verified) | Packers, virtualization, encryption; these require payment or changes to the build chain. BLA's pitch is "format-native, no commercial packer or LLVM needed", free, with one npx command |
| Anthropic refuses reverse-engineering / cloning requests in Claude Code | Big-company features | First 2026-11 (Tom's Hardware / TechPowerUp, 11-02) | Covers all Claude users | Blocks from the model side, not the publisher's side; attackers bypass it by switching to open-source models. BLA is a layer the publisher controls |

**Takeaway** : Earlier similar projects did exist (antirea and DeRea came 3~4 days before), but they all stalled at a few dozen stars. BLA wasn't the first to try; it was the first to build a product as complete as REA's and get the spread.

### 4. Growth tactics (by time)

| Time (UTC) | Event | Evidence | Confirmed? |
|---|---|---|---|
| 10-25 | Created the repo, published to npm (271 downloads on day one), launched the bla.tools site (bla-site repo created the same day); the README was in 22 languages from the start | GitHub, npm, and Brave search return README versions in each language, "2 weeks ago" | Confirmed |
| 10-27 | The author posted an "open-source promo" on **linux.do** : "REA is everywhere; as an indie dev, my answer is to confuse it!", telling the copying story and explaining the naming (re=red, bl=blue). Replies: "Serious bookmark, star, fork, four-in-one" | feedbbs.com/linuxdo/178182 | Confirmed |
| 10-27~28 | English AI aggregator sites began listing it (mindpattern 10-27, aisignal.dev 10-28) | Exa search | Confirmed |
| 10-29 | Security-circle X account @0x0SojalSec (21:10) and @blackorbird reposted: "You've seen REA tear apps apart… Someone built the defense"; Chinese blog lijianfei.com and Korean doppingcastle wrote long posts | x.com original post (read via Jina), Exa | Confirmed (follower counts for these accounts not verified) |
| 10-30 | A Sina / Weibo account posted "adding an anti-AI-decompilation shield to binaries" (09:49 Beijing); @ipurple (Panos Gkatziroulis, red-team circle) reposted (09:56); Chinese account @NFT_Chen posted a hit-template post with emojis (12:26); Guluji: "The hottest GitHub project today lets agents reverse-engineer any software; the same day someone released a shield specifically against it"; offsecblog and aifrontierpost tutorials. +398 stars that day | sina.cn, x.com, guluji.ai, Exa | Confirmed |
| 10-31 | **+738 stars in a single day** , #15 on Trendshift's daily chart; Kitploit, The Daily Commit, Reveneau, AiBoss, Dieadai AI navigation and other aggregators followed; 1028 npm downloads that day | GitHub library, README badge, Exa, npm | Confirmed |
| 11-01~03 | LinkedIn post "A GitHub security tool just crossed 1,700+ stars in about a week", reamcp.dev listing it as REA's "defense use case", explainx.ai writing "612x token claim checked", wpnews | Jina / Exa | Confirmed |
| 11-06 | Added to the Awesome REA list (AIshihzong/awesome-reverse-engineer-anything; the maintainers came to submit PR #111 adding the badge) | GitHub Issues / README | Confirmed |

**Breakdown** :

1. **Rides the biggest name (REA)** . The name BLA is aimed directly at REA, with the slogan "Make reverse engineering bankrupt again". The README's first line reads "REA reverse-engineers release artifacts in one command. BLA is the Counter-REA half". Every reshared post follows the same title pattern: "You've seen REA take apart an app — someone built the defense." Anyone searching for REA or writing about REA mentions it in passing (reamcp.dev lists it directly as a REA use case).

2. **Ignites in the Chinese community first, then goes global** . Self-promotion on linux.do (10-27) → Weibo / Sina, Chinese X accounts, Gulluji (10-30). On the English side it's security-circle X accounts (@0x0SojalSec, @blackorbird, @ipurple) plus AI aggregator sites. No HN or Product Hunt posts found (none in the hackernews database). A Reddit r/gamedev thread, "For those scared of REA and getting cloned", is visible in search results, but the body is hidden by Reddit 403, and the poster is unverified.

3. **README engineering built for spread** : READMEs in 22 languages, a comparison image (REA cracking an unhardened artifact vs a hardened one), a Trendshift badge, a table that separates "measured vs estimated" (praised specifically by the Sina post and explainx, who said "they didn't mix the two"), a one-line `npx bla-agents harden .`, and "Tell your agent: Harden my software against REA".

4. No evidence of paid acquisition, promoted posts, or star-buying bots found. The fork rate of 13% is high, which relates to the community habit of "starring, forking, and keeping it seriously" and to people who want to modify it.

### 5. Why it took off

1. **Timing** : REA gained 240k stars over 10-09–10-16 in a week, and the anxiety "AI can copy your app in minutes" became a common talking point. BLA launched on 10-25, right while REA's heat was still high and the defensive side was empty (github database: REA is at 10-25 with 380k stars and still adding more than 5000 per day).

2. **Owns the position** : among dozens of REA-adjacent repos, it is almost the only defender that got real traction. The earlier antirea and DeRea had only 36 / 45 stars, despite launching 4 days sooner. The "attack and defense in the same week" storyline is itself something media like to write about (the exact headline wording from Gulluji).

3. **Product form mirrors REA exactly** : MCP + skill + one npx command, letting Claude Code / Cursor / Codex run it themselves. Users think "however you use REA, you use BLA the same way".

4. **A credible "measured" narrative** : real REA was run in red-team tests, listing for each format which REA resource limit was triggered (ASAR header 16 MiB, GGUF nesting 32 levels, etc.), and it honestly marks which cases weren't verified. Security circles were willing to share it for two reasons: this honesty, and the memorable slogan about "poisoning, exhaustion, and hallucination".

5. **The author moves fast** : shipping up to 3.0 in two weeks, with dense PRs and releases. External contributors started joining, and stars kept rising 100–190 per day even after the peak.

### 6. Differentiation

- Compared with traditional obfuscation and packing (javascript-obfuscator, Jscrambler, VMProtect): **the target has shifted to LLM agents** . The goal is not to make code unreadable to humans, but to exploit agent weaknesses (limited context and budget, trusting decompiled output, triggering security refusals when it sees fake keys) so it overspends, goes off track, or stops on its own.

- Compared with other anti-REA side projects of the same period: **broader format coverage** (a dozen-plus formats), **a measured table run against real REA** , **a complete delivery package** (npm, MCP, skill, website, 22 languages), and a name that targets REA directly.

- **Is this why it took off?** Partly. What really mattered was the positioning as "REA's counterpart" plus being the first to deliver a complete execution. Technically, the difference (precisely overflowing the resource limits REA's documentation describes) gave security circles a reason to share and gave media something to write about. But the difference is fragile. An X comment says, "This is the same packer arms race again. Once agents get debuggers and bigger budgets, the margin shrinks fast", and another says, "At heart it's still obfuscation with a different target." If REA changes its limits, many of these "measurements" stop working.

### 7. How many people know about it

- **Spreading in small circles and starting to leak out** : the Chinese developer community (linux.do, Weibo / Sina, Gulluji, various AI navigation sites), English-language security X accounts, a dozen-plus AI news aggregators, and LinkedIn have all written about it. It did not reach the HN front page, and no major tech media outlet covering it specifically was found. No revenue involved (open source, MIT).

- **Copycats** : HMAKT99/reashield (10-31 created the repo, 2 stars, but 904 weekly npm downloads; the author promotes it with a long post on dev.to). The anti-REA space also includes earlier entries such as antirea, DeRea, and the web-side DYGK. The space is not yet crowded, but "anti AI reverse engineering" is already recognized as a category (a linux.do reply says "there's definitely a market", and Gulluji says "it will become a standard like anti-scraping").

### 8. What others can learn

- **Build a counterpart or companion to a hit** : once a repo blows up to hundreds of thousands of stars, the "uses it" side fills up with add-ons quickly, but the "defends against it" and "treats its side effects" sides are often empty. A name and slogan aimed directly at the hit means every article about it will mention you too.

- **Copy the hit's delivery format** : the hit is MCP + skill + one command, so ship it the same way and users face no learning curve.

- **Self-promote first in the Chinese community (linux.do's open-source promotion tag) to get seed stars and feedback, then let security and AI X accounts and aggregators carry it forward** . Multilingual README, measured and estimated results written separately, paired comparison images.

- **Open with a personal story like "I got copied and wanted revenge"** , which spreads better than just describing features.

### 9. Still unclear

- Actual usage: it's unclear how many of the 3000 weekly npm downloads come from real users versus CI and mirrors. The real protective effect has only been reproduced by the author (explainx says the same), and "612x tokens" is an estimate.

- Unknown: how many followers @0x0SojalSec, @blackorbird, @ipurple, and @NFT_Chen each have, and how many stars each brought in. The identity behind the original Weibo account wasn't found. The Reddit r/gamedev poster's identity and the thread's reach aren't visible (403).

- Whether REA's author will change the resource limits, or add a feature to detect BLA's decoys, which could quickly invalidate BLA's measurements.

- Whether there is organized star-buying or mutual-star exchange: no evidence found, and not ruled out.

### Sources

- GitHub API: repos/qybaihe/bla, users/qybaihe, repos/morluto/rea, issues (2026-11-06 queries)

- Our github database repo_day / repo_profile (2026-10-09–11-06); hackernews database story

- npm: api.npmjs.org/downloads/range/2026-10-25:2026-11-05/bla-agents; registry search

- linux.do self-promotion post: [feedbbs.com/linuxdo/178182](https://feedbbs.com/linuxdo/178182) (2026-10-27)

- X: [x.com/0x0SojalSec/status/2115914269661515980](https://x.com/0x0SojalSec/status/2115914269661515980) (10-29), [x.com/blackorbird/status/2115823872968888485](https://x.com/blackorbird/status/2115823872968888485), [x.com/ipurple/status/2116106838026473768](https://x.com/ipurple/status/2116106838026473768) (10-30), [x.com/NFT_Chen/status/2116144680304091539](https://x.com/NFT_Chen/status/2116144680304091539) (10-30), [x.com/LLMpsycho/status/2116897457200361905](https://x.com/LLMpsycho/status/2116897457200361905)

- Sina: [www.sina.cn/news/detail/5359655777995226.html](https://www.sina.cn/news/detail/5359655777995226.html) (10-30)

- Gulluji: [guluji.ai/square/discuss/cmvurghx3002q5wjtokallp1a](https://guluji.ai/square/discuss/cmvurghx3002q5wjtokallp1a) (10-30)

- explainx:[explainx.ai/blog/bla-blind-llm-agents-counter-rea-shield-git…](https://explainx.ai/blog/bla-blind-llm-agents-counter-rea-shield-github-trending-1981-stars-claimed-vs-verified-2026)(11-03)

- LinkedIn:[www.linkedin.com/posts/arthirajendran_github-qybaihebla-bla-…](https://www.linkedin.com/posts/arthirajendran_github-qybaihebla-bla-blind-llm-activity-7522655643858534400-p-xZ)(11-01)

- dev.to REAShield:[dev.to/arun_kumart_22e9a9959b10/an-ai-agent-can-reverse-engi…](https://dev.to/arun_kumart_22e9a9959b10/an-ai-agent-can-reverse-engineer-your-entire-repo-app-in-10-minutes-thanks-to-rea-so-i-built-451o)(11-01)

- Trendshift:[trendshift.io/repositories/323569](https://trendshift.io/repositories/323569);reamcp.dev:[reamcp.dev/en/cases/bla-b50c89](https://reamcp.dev/en/cases/bla-b50c89)

- Other aggregators: offsecblog, aifrontierpost, kitploit, thedailycommit, reveneau, aiboss88, diedong, lijianfei.com, doppingcastle (Exa search, 10-29–10-31)

This article was written by AI from public data and the data we collect daily. Numbers are sourced, and inferences are labeled.