REA MCP
☰
ZH-TW
● — 人在線上 · 瀏覽 — 次
贊助提交案例
X 貼文 · 發布者 explos1ve

這絕對是我見過最令人毛骨悚然的事情,有人打開了一個閉源

一篇貼文描述將 REA 與 AI 模型結合使用,來解釋使用者擁有或獲准檢查的應用程式功能是如何實作的,並引用 REA 的展示案例:從編譯後的二進位檔中還原了一個遊戲函式,並通過了 3,205 個測試。

e
explos1ve@explosss1ve

1/

THIS IS STRAIGHT UP THE CREEPIEST THING I'VE EVER SEEN someone opened a closed-source app and pointed Opus 5.5 at it with REA connected. it never asked for the source code. it didn't need it. it just started explaining how the app was built. feature by feature. from the button you click, down to the exact function that does the work. with evidence for every claim. in ONE afternoon. the thing companies spend years and entire legal teams protecting got read out loud by a chat window. and 99% of people have no idea this just happened. here's the whole thing. it fits in 4 lines: → open an app you own or are allowed to inspect → point Opus 5.5 at it with REA connected (it's literally called Reverse Engineer Anything) → ask how one feature actually works → read the answer that's it. Opus 5.5 does the rest. and it's not a party trick: in REA's own showcase, one function from an old game was recovered straight from the compiled binary. it passed 3,205 test cases and compiled back to the exact same bytes. now think about what this used to cost. in the 80s, Compaq did this to IBM. two teams. a room full of lawyers. months. back then, reverse engineering took entire teams and months of painstaking work. today, a single AI session can do in an afternoon what used to require an army of engineers. so how many $100M startups are protected by nothing except the fact that nobody has tried to reverse engineer them yet?

已翻譯

關於這個案例

這絕對是我見過最令人毛骨悚然的事情

有人打開了一個閉源應用程式,在連接了 REA 的情況下把 Opus 5.5 指向它。

它從未索取原始碼。 它根本不需要。

它只是開始解釋這個應用程式是如何建構的。一個功能接著一個功能。 從你點擊的按鈕,一直到完成工作的確切函式。 每個說法都有證據。

只用了一個下午。

公司花費數年時間和整個法律團隊保護的東西 被一個聊天視窗大聲讀了出來。

而 99% 的人根本不知道這件事剛剛發生了。

這就是全部。四行就能說清:

→ 打開一個你擁有或獲准檢查的應用程式 → 在連接了 REA 的情況下把 Opus 5.5 指向它(它的名字就叫 Reverse Engineer Anything) → 詢問某個功能實際是如何運作的 → 讀取答案

就這樣。剩下的由 Opus 5.5 完成。

而且這不是什麼派對把戲:在 REA 自己的展示中,一個老遊戲中的某個函式直接從編譯後的二進位檔中被還原出來。它通過了 3,205 個測試案例,並重新編譯回完全相同的位元組。

現在想想這過去要花多大代價。

在 80 年代,Compaq 對 IBM 就這麼幹過。 兩個團隊。一屋子律師。好幾個月。

那時候,逆向工程需要整個團隊和數月艱苦細緻的工作。

今天,一次 AI 工作階段就能在一個下午完成過去需要一支工程師大軍才能完成的事。

那麼,有多少估值 1 億美元的初創公司,除了還沒人嘗試逆向工程它們之外,其實什麼保護都沒有?

安裝設定

安裝方式請查看原始來源。

原文 / README

THIS IS STRAIGHT UP THE CREEPIEST THING I'VE EVER SEEN

someone opened a closed-source app and pointed Opus 5.5 at it with REA connected.

it never asked for the source code. it didn't need it.

it just started explaining how the app was built. feature by feature. from the button you click, down to the exact function that does the work. with evidence for every claim.

in ONE afternoon.

the thing companies spend years and entire legal teams protecting got read out loud by a chat window.

and 99% of people have no idea this just happened.

here's the whole thing. it fits in 4 lines:

→ open an app you own or are allowed to inspect → point Opus 5.5 at it with REA connected (it's literally called Reverse Engineer Anything) → ask how one feature actually works → read the answer

that's it. Opus 5.5 does the rest.

and it's not a party trick: in REA's own showcase, one function from an old game was recovered straight from the compiled binary. it passed 3,205 test cases and compiled back to the exact same bytes.

now think about what this used to cost.

in the 80s, Compaq did this to IBM. two teams. a room full of lawyers. months.

back then, reverse engineering took entire teams and months of painstaking work.

today, a single AI session can do in an afternoon what used to require an army of engineers.

so how many $100M startups are protected by nothing except the fact that nobody has tried to reverse engineer them yet?

更多類似作品