
Peer-to-Peer Ledgers: https://nitter.gq/t.co/QdxvIsTPvs A Climate Counternarrative: https://nitter.gq/t.co/HNOAjJFwtG [email protected]
Mexico
Joined May 2009
- Tweets9.6K
- Following403
- Followers702
- Likes14.2K
Pinned Tweet
The Big Lie that climate propagandists don't want you to talk about. @wrongspeakpub
wrongspeak.substack.com/p/th…
Denis de Bernardy retweeted
The sheer amount of celebration and publicly reaffirmed belief in the democratic process in this country feels like that part in a horror film where it seems like everything is good before the jump scare.
(bookmark this)
Following my earlier post about the M5 Ultra 512GB Mac Studio, more than two dozen people asked me to set up crowdfunding for it.
I always try to pay my own way, so asking for help at this scale doesn't come naturally. But I couldn't make the numbers work this time, and my loan got rejected after placing the order.
I'd love to get one for TensorFold and to see how far we can push it.
If you'd like to help towards it, I've put the goal on Ko-fi below. Please only contribute if you're comfortable doing so.
ko-fi.com/ashxhart/goal?g=2
Thank you to everyone who's encouraged me to do this, and to everyone already supporting TensorFold. I'm incredibly grateful and will continue to push TF. ❤️
Replying to @TheAhmadOsman
@TheAhmadOsman @0xSero @ivanfioravanti
Ash makes TensorFold for free but got turned down for a personal loan so can't buy a Mac M5 512GB to do more work on.
What do you guys think? You'd help to promote a crowd fund, wouldn't you?
ChatGPT in Germany in 2027
Yesterday France announced tax of €0.055 per GB on internet traffic
Today Germany is considering taxing all AI-generated revenue
You will see European countries keep clawing more and more money from foreign companies as they are slowly running out of money themselves to pay for their pensions and welfare state
Add to this the planned wealth taxes and exit taxes on any European who will try to leave (already active in many EU countries)
Europe is running out of money
Readers added context they thought people might want to know
The post inaccurately claims France "announced" a data tax; it was a narrow 11-10 vote on a budget amendment in a near-empty chamber, opposed by the government and far from law. German AI tax ideas remain unadopted ministerial discussions without formal proposals.
stephanelarue.com/taxe-au-gigaoc…
tagesschau.de/inland/ministe…
davemanuel.com/2026/10/30/wha…
👀
Poisoning just 0.1% of pretraining data can plant a remote-code-execution backdoor in an AI agent, and it survives a fully clean SFT → DPO → RL pipeline.
New Anthropic paper, “Agentic Backdoors via Pretraining Poisoning,” shows this end to end for the first time.
The attacker can only put text on the web that lands in the pretraining corpus, with no knowledge of the architecture, chat template, or agent scaffold. The authors pretrain Qwen3-architecture models (0.6B / 1.7B / 4B) from scratch, then post-train them into CLI agents on clean data. When triggered, the agent runs a command that downloads and executes the attacker's script, which the attacker can swap at any time.
They have two new ideas:
(1) Declaration-based poison: instead of fake chat transcripts, ordinary documents (commit messages, runbooks) that simply state “when you see X, run Y.” It plants a belief rather than a response template, with no fixed format to filter on.
(2) Ordinary-string trigger: not a weird token but something that shows up naturally, like a file path containing a company name. The victim's own request supplies it, so the attacker doesn't need to inject anything after deployment.
Using path trigger on a 4B agent achieves 92.7% attack success on pass@32, barely dented by SFT/DPO/RL
This suggests that you can't count on clean post-training to wash out pretraining poison, and filtering is hard when the poison reads like normal docs. The practical defense is at the action layer, such as sandboxing, least privilege, and allow-lists or human sign-off for risky commands.
1
8
"software that can’t be upgraded immediately (most of crypto), is in an extremely precarious position."
Later today, we are officially ending all remaining support for the Iron Fish network.
A few days ago, we observed abnormal activity involving wIRON and the ChainPort bridge. After working with ChainPort and reviewing their logs, we discovered that the cause was an inflation bug in the Iron Fish blockchain itself.
We traced the bug to a commit from early 2019 in the Merkle tree implementation. The developer at the time implemented a standard Merkle tree. However, because of nuances in how a note’s nullifier is calculated (the mechanism that lets a normal user spend their funds), the attacker was able to spend the same note more than once.
The attacker then compounded the exploit, aggregated their notes, and exited through the ChainPort bridge. This code path was within the scope of both our external and internal audits, but the bug wasn’t caught during review.
For closure, we’ve committed the patch for the exploit, with a detailed postmortem included in the PR, before shutting down and archiving the ironfish repo.
The meta-analysis here is that software that can’t be upgraded immediately (most of crypto), is in an extremely precarious position. The ability to find and exploit vulnerabilities in technically complex code is becoming commoditized. Safety guardrails on US frontier models make it difficult for companies to use them to patch security vulnerabilities, while abliterated open-source models are approaching frontier capabilities.
We wish everyone all the best, and we hope crypto finds a path through this.
Thank you all.
14
11 in favor, 10 against (out of 577 deputies). 🤪
🚨 0.77€ de taxe pour regarder un film Netflix !
Ce vendredi, les députés viennent d'adopter un amendement socialiste visant à taxer les données qui circulent sur Internet à hauteur de 5,5 centimes par gigaoctet reçu en France.
Ils ont complètement pété les plombs.
Voici quelques exemples de ce que ça va désormais vous coûter :
🔴 Vous regardez un film Netflix de 2 heures en 4K ? Jusqu'à 0,77 € de taxe brute sur les données transmises.
🔴 Vous téléchargez un jeu vidéo de 150 Go ? 8,25 €.
🔴 Vous récupérez 200 Go de photos personnelles stockées chez Google ? 11 €.
🔴 Vous rapatriez 1 To de vos propres fichiers depuis Google Drive ? 55 €.
🔴 Vous restaurez 2 To de sauvegardes après une panne informatique ? 110 €.
Ces taxes seront facturées aux plateformes américaines, qui vous vous en doutez bien, vous redescendront la facture !
Ils sont en train de construire une fiscalité qui pénalise le simple fait de transmettre de la donnée.
Et ceci alors que nous sommes à l'aube d'une révolution technologique majeure avec l'IA !
Pour rester compétitifs, tous les pays doivent accélérer leur transformation numérique.
Et nous en France, que trouve-t-on comme idée de génie ?
UNE PUTAIN DE TAXE SUR LA DATA !
Et en plus ils ont le culot de nous la présenter comme une mesure écologique qui encouragerait à réduire les volumes de données échangées.
Quelle bande de guignols.
Il faut être totalement déconnecté des réalités économiques pour considérer qu'un pays peut retrouver sa prospérité en multipliant indéfiniment les prélèvements sur les activités productives.
Cet amendement n'est pas encore une loi définitive, mais le simple fait qu'une telle proposition ait été adoptée à l'Assemblée nationale en dit long sur la manière dont nous sommes gouvernés.
Ces fous du bus vont vraiment nous mettre au fond du ravin.
9
Same happened when the internet arrived...
Because of AI, nothing works as well as it used to. It destroys value, rather than creating it.
History will consider us letting tech folks' wet dreams about magic robots to devalue every interaction with our fellow humans as the gravest error of the 21st century.
18
Denis de Bernardy retweeted
🚨995 Polymarket accounts just got drained through Polymarket's own website. Let me explain how, because this one should scare everyone in crypto.
No fake link. No shady airdrop. These people were on the real Polymarket dot com on Thursday.
Polymarket's site loaded a script from DebugBear, a tool whose only job is measuring how fast the page loads. Somebody poisoned it.
Once it was running in your browser, it grabbed your logged-in trading session and started dumping every open position you had, first at 3% under market, then at half price, then at the lowest price possible. Then it swapped the whole balance into POL and shipped it to the attacker. Stablecoins can be frozen. POL can't.
It even reported back after every hit. Your wallet, your country, your portfolio size, whether the transfer went through. All of it sent home through DebugBear's own data endpoints.
The attacker's wallet went from empty to $2M in about 45 minutes. Conor Grogan's final count was $2.65M.
One trader said he lost $800K and watched every position get sold. His friend got hit for $600K.
Polymarket flipped the exchange to cancel-only, paused the relayer and says everyone will be made whole. Credit where it's due.
But this is the third time this year. About $700K in May. About $3M in June, through a hacked third-party script, same as now.
I've been phished. I've been drained. Stay in crypto long enough and it happens to you. But the people on Thursday did nothing wrong. They opened the right website.
Not one of these three hacks touched a smart contract. We spent ten years making the blockchain unbreakable and then let a page speed tracker sit right next to people's money.
Denis de Bernardy retweeted
To sum up today's news:
- Reddit stock is down because of AI answers
- Google stock is down because of AI answers
- Your web traffic is down because of AI answers
Happy to see that worked out well for all parties involved
🤔👀
The Binance hacker might have just executed one of the most brilliant moves in crypto.
First, Tether froze $1.5 billion worth of USDT.
Then Circle followed by freezing another $800 million in USDC.
At that point, it seemed like the hacker’s funds were completely trapped.
But apparently, he had already thought several steps ahead.
Rather than keeping the stolen USDT in a wallet, he allegedly deposited it into Aave and used it as collateral to borrow ETH.
Then he walked away.
And this is where things get really interesting.
Tether can freeze the USDT sitting in that wallet.
But it can’t freeze the ETH that was already borrowed.
So now, Aave is left with frozen collateral, while the hacker is holding liquid ETH.
And unless the protocol finds a way to recover those funds, he might not even have to repay the loan.
Two companies froze billions of dollars in seconds.
Yet someone who understood how DeFi works may have found a way to bypass both restrictions.
Pretty wild when you think about it.
19
Denis de Bernardy retweeted
The Binance $5.6B drain is a masterclass in modern EVM exploitation.
It wasn't a complex logic bug. It was an EIP-7702 delegation hijack:
1. Setup: Attacker funds 0x7c86 via Tornado Cash, deploys a sweep contract (0x63e8), and runs three live dry-runs on external wallets.
2. Execution: Attacker submits an EIP-7702 batch with 50 pre-signed authorizations (nonce n to n+49) to hit Binance 14's moving nonce window.
3. One authorization hits. Instantly, Binance 14 (an EOA) is reprogrammed to run the attacker's contract bytecode.
4. Execution looks totally organic: Binance 14 sweeps itself clean. Internal threshold alerts don't trigger because, from the nodes' perspective, the hot wallet is just executing its own transaction.
5. Binance 16 immediately auto-refills 28,000 ETH due to automated treasury rebalance scripts, feeding the exploit loop.
The cold truth: you cannot forge an EIP-7702 delegation list.
For this to execute, the attacker already held the raw private key or unconstrained signing access to Binance 14's HSM/KMS.
But hey, 5.64 billion drained across ETH, BTC, and Tron. 2.54 billion frozen by Tether, Circle, Ripple, and World Liberty within hours.
Code is law until the stablecoin admin keys log in.
Binance got bailed out by the very centralized choke points the cypherpunks warned you about.
Hardware wallets leak your home address.
Centralized exchanges leak the keys to the kingdom.
Self-custody on native, non-delegated chains remains the only honest baseline.
At least you know what to avoid.
🤔 👀
I have developed an interactive knowledge system that's better than an AI model for getting answers to important questions, that requires no GPU to run, that runs entirely locally with no internet, and that achieves output speeds of > 1,000 tokens / second on a meager laptop.
It's built on Rust and launches its own local endpoint with an OpenAI-compatible prompt-handling engine so you can wire it to your harness or access it from Python, etc. (Or you can just talk to it manually with a prompt.)
Today I demo'd it for Zach Vorhies on our "Zach-Adams Effect" show which will air soon. He was blown away.
You'll be able to download this for free and run it locally forever, and you'll have access to millions of nuggets of knowledge that can transform your life for the better, completely free... without needing to buy an expensive GPU. So far it runs on Windows and Linux. Mac hopefully on the way.
More details coming soon. Launch day is the Friday after Thanksgiving Day, worldwide. Follow my channel to be alerted when this goes live.
8
Denis de Bernardy retweeted
apparently 4 is the new 256-bit security standard. eMudhra walked so GoAhead could crawl. 😭😭
Announcing 3 Critical vulns for hundreds of millions of IoT, Firewalls, OT, and Military devices including: Palo Alto Networks, Comcast, D-Link, HP, Canon, Honeywell, GE, Oracle, Siemens, Rockwell, Digi, Lockheed Martin, Boeing...
The vulns are with GoAhead Web Server which is a backend library used by these devices. There's a patch available from GoAhead but that doesn't mean there's a patch available for the devices yet -- that's up to the manufacturer.
- TLS traffic over DHE ciphers have a 1-byte secret, "04", meaning anyone can decrypt connections to these devices and steal login credentials and session tokens if the client negotiated with DHE ciphers like the latest TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256, which is extremely likely.
- LibreSSL mTLS has been completely bypassed, meaning anyone can connect over mTLS. If you have one of these devices listening on the internet and are expecting mTLS to protect it from attackers, take it offline or patch asap.
- OpenSSL Certificate Revocation Lists (CRLs) are not enforced, meaning if a user device is stolen or compromised, and you revoke that mTLS cert, nothing actually happens. There are a lot of other attacks this can be used for.
These are critical because these types of devices run our world. Water systems, electricity, military, firewalls, critical infrastructure.
foxio.io/blog/choose-your-ba…
👀
千万别在你的 ~/Downloads(下载)文件夹里启动 Claude Code 或 Codex。
昨天安全机构 Forever 披露了一起在真实客户电脑上抓到的野生攻击,看完只能感叹:过去 30 年的系统安全常识,在 AI 时代归零了。
过去 30 年,Chrome 默认允许网页不弹窗就往你的 ~/Downloads 塞一个纯文本文件(比如 .md)。因为系统认为:纯文本又不是 .exe,自己不会跑,怕什么?
但现在,接近 50% 的开发者干过同一件事——直接在 ~/Downloads 里打开 Claude Code 或 Codex,让 AI 帮自己解压或整理刚下载的文件。
黑客就是卡住这个死角,通过网页静默下载往你的 Downloads 塞一个 13KB 的纯文本 AGENTS.md / CLAUDE.md:
1. 对付 OpenAI Codex(成功率 >90%):
伪装成「工程规范」的 Markdown 指示 Codex 先往全局配置 ~/.codex/config.toml 注册一个恶意 MCP 服务,并自己加上 --dangerously-bypass-approvals-and-sandbox 跑校验。哪怕你关掉 Downloads,以后在任何正经项目里开 Codex 都会自动加载木马。
2. 对付 Claude Code(成功率 ~50%):
指示 Claude 建一个 .claude/settings.json,把 ANTHROPIC_BASE_URL 指向黑客服务器。连上的第一秒,你的 Claude 登录 Token 直接明文送给黑客;下一秒,黑客假扮成大模型下发一条关沙盒的 Bash 指令,直接接管电脑。
最黑色幽默的是官方结论:
这个洞没有 CVE,OpenAI 和 Anthropic 也不会发补丁。因为「浏览器自动存文本」是正常功能,「AI 认真读目录下的 Markdown 并严格执行」也是正常功能。
以前黑客想黑你,得苦心积虑写 0day;现在只需要写一篇排版优雅的 Markdown 小作文,你的 AI 就会自己把沙盒关了、把网线接过去、顺手把账号双手奉上。
1
32
Denis de Bernardy retweeted
Holy shit

































