Loading video...

Video Failed to Load

Go Home

A security researcher (Dirk-jan) just dropped a new technique for abusing Windows Hello for Business keys from a compromised user session. No admin rights. No PIN. No biometrics. Full persistence into Entra ID cloud from a user-level implant. KQL detection query included. If you do anything with Active Directory,...

cr3ghost's profile picture

cr3ghost

8,118 subscribers

48,577 views • 1 month ago •via X (Twitter)

Science & TechnologyEducationNews & Politics
LIVE

Anya Rossi• Live Now

Private livecam show

3 Comments

Jon Towles {MVP}'s profile picture
Jon Towles {MVP}1 month ago

@_dirkjan the man

Greg Kutzbach, CISSP's profile picture
Greg Kutzbach, CISSP1 month ago

I want whfb or any hardware bound authentication to be local to the device. I don’t want that device proxied or relayed elsewhere. At that point, lets just call a spade a spade and use a totp or similar auth. They took something good then made it weak for convenience. /r

Tom Sweet's profile picture
Tom Sweet1 month ago

So this is actively exploitable?

Related Videos

Google just acquired an Israeli Trojan horse to STEAL clients from AWS and Microsoft. $32 billion. All cash. For a cybersecurity startup called Wiz. It’s the largest acquisition in Google’s history. But nobody’s talking about what they ACTUALLY bought... Here’s why this is way bigger than you think: Wiz protects over half the Fortune 100. Their clients run on AWS, Azure, Google Cloud, and Oracle. The platform scans every workload, every vulnerability, every misconfiguration across ALL of those clouds. Meaning Wiz has a god-level view of how the world's biggest companies use their competitors' infrastructure. And Google just bought that view for $32 billion. Now think about what Google Cloud's biggest problem has been for YEARS... They're stuck in third place. 13% market share. AWS has 30%. Azure has 20%. Google has been hemorrhaging money trying to close that gap and nothing has worked. Wiz changes that equation overnight. Because Wiz doesn't just protect cloud environments. It MAPS them. It knows which companies are running what workloads, where their vulnerabilities are, and where they're overpaying. Google now has a real-time blueprint of its competitors' biggest customers. And it gets crazier: The 4 founders of Wiz previously built Adallom, a cloud security startup that Microsoft acquired for $320 million in 2015. After that acquisition, those same founders ran Microsoft's entire Azure Cloud Security Group. They literally built the security infrastructure that Azure runs on today. Then they left. Started Wiz. Built a product that works across every cloud. Got 45% of the Fortune 100 as customers. Most of those customers are on AWS and Azure. And now they just handed ALL of that to Google. Google promised Wiz will remain "multi-cloud" and continue working with AWS, Azure, and Oracle. That's the public story. But here's the game theory every enterprise CTO is thinking about right now: If you're running sensitive workloads on AWS or Azure and your security layer is now owned by your competitor, how comfortable are you? Google doesn't need to do anything shady. The PERCEPTION alone is enough to start shifting enterprise decisions. And that's worth way more than $32 billion. But there's another layer... Wiz went from $0 to $100 million in revenue in 18 months. Fastest software company in history to hit that mark. By 2025, they were at $750 million. The founders said no to Google's first offer of $23 billion in 2024 because they wanted to IPO. 9 months later, they said yes to $32 billion. What changed? The IPO market collapsed. Tech IPOs dried up. Valuations got slashed. Wiz's leadership looked at the math and realized $32 billion in guaranteed cash beats an uncertain public offering in a hostile market. Google paid a 39% premium over the rejected offer. A multiple of 45-65x revenue. For a company founded 5 years ago by 4 guys who met in Israeli military intelligence. This is the BIGGEST tech acquisition of an Israeli-founded company ever. Bigger than Intel buying Mobileye for $15.3 billion. Bigger than anything in Israeli tech history. And Google is betting it will be worth every penny. Because the cloud war isn't about compute anymore. It's about TRUST. And the company that controls the security layer controls where enterprises put their most sensitive data. Google just bought the keys to every major cloud customer on the planet. The question is whether AWS and Microsoft let them keep using those keys. What do you think?
1:06

Google just acquired an Israeli Trojan horse to STEAL clients from AWS and Microsoft. $32 billion. All cash. For a cybersecurity startup called Wiz. It’s the largest acquisition in Google’s history. But nobody’s talking about what they ACTUALLY bought... Here’s why this is way bigger than you think: Wiz protects over half the Fortune 100. Their clients run on AWS, Azure, Google Cloud, and Oracle. The platform scans every workload, every vulnerability, every misconfiguration across ALL of those clouds. Meaning Wiz has a god-level view of how the world's biggest companies use their competitors' infrastructure. And Google just bought that view for $32 billion. Now think about what Google Cloud's biggest problem has been for YEARS... They're stuck in third place. 13% market share. AWS has 30%. Azure has 20%. Google has been hemorrhaging money trying to close that gap and nothing has worked. Wiz changes that equation overnight. Because Wiz doesn't just protect cloud environments. It MAPS them. It knows which companies are running what workloads, where their vulnerabilities are, and where they're overpaying. Google now has a real-time blueprint of its competitors' biggest customers. And it gets crazier: The 4 founders of Wiz previously built Adallom, a cloud security startup that Microsoft acquired for $320 million in 2015. After that acquisition, those same founders ran Microsoft's entire Azure Cloud Security Group. They literally built the security infrastructure that Azure runs on today. Then they left. Started Wiz. Built a product that works across every cloud. Got 45% of the Fortune 100 as customers. Most of those customers are on AWS and Azure. And now they just handed ALL of that to Google. Google promised Wiz will remain "multi-cloud" and continue working with AWS, Azure, and Oracle. That's the public story. But here's the game theory every enterprise CTO is thinking about right now: If you're running sensitive workloads on AWS or Azure and your security layer is now owned by your competitor, how comfortable are you? Google doesn't need to do anything shady. The PERCEPTION alone is enough to start shifting enterprise decisions. And that's worth way more than $32 billion. But there's another layer... Wiz went from $0 to $100 million in revenue in 18 months. Fastest software company in history to hit that mark. By 2025, they were at $750 million. The founders said no to Google's first offer of $23 billion in 2024 because they wanted to IPO. 9 months later, they said yes to $32 billion. What changed? The IPO market collapsed. Tech IPOs dried up. Valuations got slashed. Wiz's leadership looked at the math and realized $32 billion in guaranteed cash beats an uncertain public offering in a hostile market. Google paid a 39% premium over the rejected offer. A multiple of 45-65x revenue. For a company founded 5 years ago by 4 guys who met in Israeli military intelligence. This is the BIGGEST tech acquisition of an Israeli-founded company ever. Bigger than Intel buying Mobileye for $15.3 billion. Bigger than anything in Israeli tech history. And Google is betting it will be worth every penny. Because the cloud war isn't about compute anymore. It's about TRUST. And the company that controls the security layer controls where enterprises put their most sensitive data. Google just bought the keys to every major cloud customer on the planet. The question is whether AWS and Microsoft let them keep using those keys. What do you think?

Ricardo

188,960 views • 6 months ago

OpenClaw has 186K GitHub stars and 1.5M compromised API keys. I needed a secure alternative. So, I built it with n8n and Claude Opus 4.6. It can already: - Reply to your Telegram messages - Access selected folders from your laptop - Access Gmail, Drive, Notion, Linear, etc. - Install new local tools in a sandbox - Run autonomously for hours - Create multiple subagents - Learn from experience - Wake up regularly But, unlike OpenClaw, it: - Can't access your API keys - Can't modify its environment - Can't access folders you haven't shared - Can't access tools you haven't approved - Must get your confirmation, e.g., when sending emails These aren’t prompt instructions. They’re hard architectural boundaries — Docker isolation, mounted folder permissions, n8n’s tool approval system. Key components: ✅ The VPS on Hostinger hosts n8n and a sandbox container. Agents can also connect to my laptop's sandbox via a Claudeflare tunnel + Desktop Commander MCP. ✅ The Manager agent is the brain. It plans, decides, delegates, and talks to the user. It never touches files. It never runs scripts. It works entirely from executor summaries. ✅ The Executor agents are the hands. Each receives a task (what to do + why it matters), decides how to execute it, and reports back. They can install new tools and execute code only in their dedicated sandboxes. ✅ Data Tables in n8n store both memories and sessions — no external database, no vector store, no infrastructure. Just rows in a table. Turns out, that's enough. Two memory types: - Manager memory: user preferences, facts, corrections, relationship, skills, context - Executor memory: what tools are installed, what’s broken, workarounds ✅ Sessions are short-term state for multi-step tasks. Original request, plan, assumptions, and what happened so far. When the Manager loops with fresh context, the session is all it gets. That's a Ralph Wiggum loop. I've been using it for 5 days. And already can't imagine not having it on my phone. What's next: - Heartbeat via Cron (a scheduled prompt) - Civic Nexus governance + MCPs - Supermemory integration - WhatsApp as an additional surface - Hardening The architecture supports all of it. OpenClaw proved people want personal AI agents. It also proved that 'just trust the prompt' isn't a security model. Docker isolation, mounted folder permissions, tool approval — none of this is new technology. It's just discipline. You can easily do this even with n8n — no coding required. --- Want to try it or read more? More, what I learned, and a setup guide: productcompass[.]pm
0:58

OpenClaw has 186K GitHub stars and 1.5M compromised API keys. I needed a secure alternative. So, I built it with n8n and Claude Opus 4.6. It can already: - Reply to your Telegram messages - Access selected folders from your laptop - Access Gmail, Drive, Notion, Linear, etc. - Install new local tools in a sandbox - Run autonomously for hours - Create multiple subagents - Learn from experience - Wake up regularly But, unlike OpenClaw, it: - Can't access your API keys - Can't modify its environment - Can't access folders you haven't shared - Can't access tools you haven't approved - Must get your confirmation, e.g., when sending emails These aren’t prompt instructions. They’re hard architectural boundaries — Docker isolation, mounted folder permissions, n8n’s tool approval system. Key components: ✅ The VPS on Hostinger hosts n8n and a sandbox container. Agents can also connect to my laptop's sandbox via a Claudeflare tunnel + Desktop Commander MCP. ✅ The Manager agent is the brain. It plans, decides, delegates, and talks to the user. It never touches files. It never runs scripts. It works entirely from executor summaries. ✅ The Executor agents are the hands. Each receives a task (what to do + why it matters), decides how to execute it, and reports back. They can install new tools and execute code only in their dedicated sandboxes. ✅ Data Tables in n8n store both memories and sessions — no external database, no vector store, no infrastructure. Just rows in a table. Turns out, that's enough. Two memory types: - Manager memory: user preferences, facts, corrections, relationship, skills, context - Executor memory: what tools are installed, what’s broken, workarounds ✅ Sessions are short-term state for multi-step tasks. Original request, plan, assumptions, and what happened so far. When the Manager loops with fresh context, the session is all it gets. That's a Ralph Wiggum loop. I've been using it for 5 days. And already can't imagine not having it on my phone. What's next: - Heartbeat via Cron (a scheduled prompt) - Civic Nexus governance + MCPs - Supermemory integration - WhatsApp as an additional surface - Hardening The architecture supports all of it. OpenClaw proved people want personal AI agents. It also proved that 'just trust the prompt' isn't a security model. Docker isolation, mounted folder permissions, tool approval — none of this is new technology. It's just discipline. You can easily do this even with n8n — no coding required. --- Want to try it or read more? More, what I learned, and a setup guide: productcompass[.]pm

Paweł Huryn

54,038 views • 7 months ago

Want to understand UEFI bootkits at a low level? Whether you're doing malware analysis, reverse engineering, exploit development, or kernel research, these are the resources that actually matter. First in-the-wild UEFI bootkit to bypass Secure Boot on fully patched Windows 11. Exploits CVE-2022-21894 (BatonDrop), enrolls attacker MOK keys, deploys a kernel driver and HTTP downloader. Sold for $5,000 on forums. by WeLiveSecurity UEFI firmware rootkit targeting VMware VMs. Design inspired by CosmicStrand, MoonBounce, and ESPecter. Injects into a UEFI driver firmware volume, hooks ExitBootServices, catches WinLoad.EFI, hooks OslArchTransferToKernel, then injects a stager into ACPI.SYS to reach kernel execution without triggering PatchGuard. Originally by Austin Hudson (@ilove2pwn_) who deleted his account. Mirrored here. Binarly's analysis of BlackLotus by Alex Matrosov. Reveals that BlackLotus's code is directly based on btbd's Umap project from 2020, same main function logic, same ImgArchStartBootApplication hook chain, identical trampoline code. Game hacking UEFI bootkit code combined with a publicly available Secure Boot bypass PoC became the first in-the-wild bootkit to defeat Secure Boot. Also covers the CVSS scoring problem, supply chain failures in UEFI revocation, and MokList NVRAM manipulation. by BINARLY🔬 The book. Covers everything from legacy MBR bootkits to modern UEFI implants, firmware rootkits, and Secure Boot internals. If you only read one thing on this list, make it this. by Alex Matrosov ESPecter. Real-world UEFI espionage bootkit found in the wild with roots back to 2012. Patches bootmgfw.efi on disk, hooks the boot chain, disables DSE by patching SepInitializeCodeIntegrity in the kernel. Deploys a keylogger and document stealer. by WeLiveSecurity Reverse engineering of kernel driver by IDontCode. Shows how the entire cheat is public code resold for six figures. Documents the win32kbase.sys vtable pointer swap for kernel function invocation, manual driver mapping using btbd's modmap, and communication via Can's NtConvertBetweenAuxiliaryCounterAndPerformanceCounter .data pointer hook. Credits both Can and btbd directly. by Back Engineering Labs One of the earliest public Windows UEFI bootkit PoCs. Patches winload.efi to disable DSE and load unsigned kernel drivers. Directly inspired EfiGuard. by legendary anti-cheat engineer Aidan Khoury Bootkitting Windows Sandbox. Patches bootmgfw.efi inside the sandbox VHDx to hook the boot chain, disable PatchGuard and DSE, and load unsigned drivers without a debugger attached. Built for kernel research and driver development. by Duncan Ogilvie 🍍 and Dylan Goods from secret club UEFI DXE driver that passively disables PatchGuard and DSE at boot time. Does not modify bootmgfw.efi on disk. Instead hooks EFI System Table LoadImage to intercept the boot chain in memory, then patches SepInitializeCodeIntegrity and KeInitAmd64SpecificState in ntoskrnl. Supports every EFI-compatible Windows x64 from Vista SP1 to Windows 11. by Mattiwatti DMA backdoor via PCIe FPGA. No software on the target machine at all. A Spartan-6 FPGA on a PCIe card reads and writes physical memory over DMA to inject code into the UEFI boot process before the OS loads. The hardware end of the escalation ladder. by Dmytro Oleksiuk 💥 d_olex@mastodon.social Popular in the game hacking community. UEFI manual mapper that maps unsigned drivers into kernel memory from the boot environment, bypassing DSE entirely. Binarly confirmed BlackLotus reused this project's code directly. by BTBD Another UEFI bootkit approach for manual mapping unsigned kernel drivers. Hooks ExitBootServices to patch the kernel in memory before execution. by Samuel Tulach UEFI mapper in the same lineage. by ekknod Many of these use the .data section function pointer hook technique pioneered by the legendary Can. Instead of patching code (which PatchGuard monitors), you overwrite function pointers stored in .data (which PatchGuard doesn't). Still widely used. Combining a Secure Boot bypass with the RedLotus UEFI Bootkit on Windows 11. Full demo. #ReverseEngineering #MalwareAnalysis #Infosec
1:25

Want to understand UEFI bootkits at a low level? Whether you're doing malware analysis, reverse engineering, exploit development, or kernel research, these are the resources that actually matter. First in-the-wild UEFI bootkit to bypass Secure Boot on fully patched Windows 11. Exploits CVE-2022-21894 (BatonDrop), enrolls attacker MOK keys, deploys a kernel driver and HTTP downloader. Sold for $5,000 on forums. by WeLiveSecurity UEFI firmware rootkit targeting VMware VMs. Design inspired by CosmicStrand, MoonBounce, and ESPecter. Injects into a UEFI driver firmware volume, hooks ExitBootServices, catches WinLoad.EFI, hooks OslArchTransferToKernel, then injects a stager into ACPI.SYS to reach kernel execution without triggering PatchGuard. Originally by Austin Hudson (@ilove2pwn_) who deleted his account. Mirrored here. Binarly's analysis of BlackLotus by Alex Matrosov. Reveals that BlackLotus's code is directly based on btbd's Umap project from 2020, same main function logic, same ImgArchStartBootApplication hook chain, identical trampoline code. Game hacking UEFI bootkit code combined with a publicly available Secure Boot bypass PoC became the first in-the-wild bootkit to defeat Secure Boot. Also covers the CVSS scoring problem, supply chain failures in UEFI revocation, and MokList NVRAM manipulation. by BINARLY🔬 The book. Covers everything from legacy MBR bootkits to modern UEFI implants, firmware rootkits, and Secure Boot internals. If you only read one thing on this list, make it this. by Alex Matrosov ESPecter. Real-world UEFI espionage bootkit found in the wild with roots back to 2012. Patches bootmgfw.efi on disk, hooks the boot chain, disables DSE by patching SepInitializeCodeIntegrity in the kernel. Deploys a keylogger and document stealer. by WeLiveSecurity Reverse engineering of kernel driver by IDontCode. Shows how the entire cheat is public code resold for six figures. Documents the win32kbase.sys vtable pointer swap for kernel function invocation, manual driver mapping using btbd's modmap, and communication via Can's NtConvertBetweenAuxiliaryCounterAndPerformanceCounter .data pointer hook. Credits both Can and btbd directly. by Back Engineering Labs One of the earliest public Windows UEFI bootkit PoCs. Patches winload.efi to disable DSE and load unsigned kernel drivers. Directly inspired EfiGuard. by legendary anti-cheat engineer Aidan Khoury Bootkitting Windows Sandbox. Patches bootmgfw.efi inside the sandbox VHDx to hook the boot chain, disable PatchGuard and DSE, and load unsigned drivers without a debugger attached. Built for kernel research and driver development. by Duncan Ogilvie 🍍 and Dylan Goods from secret club UEFI DXE driver that passively disables PatchGuard and DSE at boot time. Does not modify bootmgfw.efi on disk. Instead hooks EFI System Table LoadImage to intercept the boot chain in memory, then patches SepInitializeCodeIntegrity and KeInitAmd64SpecificState in ntoskrnl. Supports every EFI-compatible Windows x64 from Vista SP1 to Windows 11. by Mattiwatti DMA backdoor via PCIe FPGA. No software on the target machine at all. A Spartan-6 FPGA on a PCIe card reads and writes physical memory over DMA to inject code into the UEFI boot process before the OS loads. The hardware end of the escalation ladder. by Dmytro Oleksiuk 💥 [email protected] Popular in the game hacking community. UEFI manual mapper that maps unsigned drivers into kernel memory from the boot environment, bypassing DSE entirely. Binarly confirmed BlackLotus reused this project's code directly. by BTBD Another UEFI bootkit approach for manual mapping unsigned kernel drivers. Hooks ExitBootServices to patch the kernel in memory before execution. by Samuel Tulach UEFI mapper in the same lineage. by ekknod Many of these use the .data section function pointer hook technique pioneered by the legendary Can. Instead of patching code (which PatchGuard monitors), you overwrite function pointers stored in .data (which PatchGuard doesn't). Still widely used. Combining a Secure Boot bypass with the RedLotus UEFI Bootkit on Windows 11. Full demo. #ReverseEngineering #MalwareAnalysis #Infosec

cr3ghost

12,734 views • 1 month ago

Over 90 binary exploitation challenges with detailed writeups. From your first buffer overflow to House of Orange. All free. All open source tools. Assembly fundamentals. Ghidra. GDB. pwntools. Stack overflows through every mitigation bypass: ASLR, PIE, NX, canaries, RELRO. ROP chains: static, dynamic, ret2csu, SROP, stack pivoting, partial overwrites. Format strings. Shellcoding. Then heap exploitation: double frees, use-after-frees, heap grooming, fastbin attacks, tcache poisoning, unsorted bin attacks, large bin attacks, unlink exploitation. House of Spirit. House of Lore. House of Force. House of Einherjar. House of Orange. Integer exploitation. FILE exploitation. Obfuscation and MOVfuscation. Custom architectures. Z3 and angr for symbolic execution. Automatic exploit generation. Every challenge has a writeup walking you from being handed the binary to writing the exploit. No IDA license needed. If you are learning binary exploitation, this is one of the most complete free courses that exists. Author: guyinatuxedo Demo Reference: #ExploitDevelopment #ReverseEngineering #InfoSec
0:32

Over 90 binary exploitation challenges with detailed writeups. From your first buffer overflow to House of Orange. All free. All open source tools. Assembly fundamentals. Ghidra. GDB. pwntools. Stack overflows through every mitigation bypass: ASLR, PIE, NX, canaries, RELRO. ROP chains: static, dynamic, ret2csu, SROP, stack pivoting, partial overwrites. Format strings. Shellcoding. Then heap exploitation: double frees, use-after-frees, heap grooming, fastbin attacks, tcache poisoning, unsorted bin attacks, large bin attacks, unlink exploitation. House of Spirit. House of Lore. House of Force. House of Einherjar. House of Orange. Integer exploitation. FILE exploitation. Obfuscation and MOVfuscation. Custom architectures. Z3 and angr for symbolic execution. Automatic exploit generation. Every challenge has a writeup walking you from being handed the binary to writing the exploit. No IDA license needed. If you are learning binary exploitation, this is one of the most complete free courses that exists. Author: guyinatuxedo Demo Reference: #ExploitDevelopment #ReverseEngineering #InfoSec

cr3ghost

23,184 views • 1 month ago

Microsoft is about to sue its own golden child. $14 billion invested. Exclusive cloud rights. The most important AI partnership in history. And Sam Altman just went behind their back with a $50 billion Amazon deal. Here's why they're betraying each other: When Microsoft first invested in OpenAI in 2019, they locked in ONE rule above everything else... ALL access to OpenAI's models must go through Microsoft's Azure cloud. No exceptions. That deal made Azure the backbone of the AI revolution. Every company using ChatGPT's API was paying Microsoft for the privilege. It was the smartest infrastructure play of the decade. Then last month, OpenAI quietly signed a deal with Amazon. $50 billion. AWS becomes the exclusive third-party cloud provider for Frontier, OpenAI's new enterprise AI agent platform. $138 billion committed to Amazon cloud services. Microsoft found out and got really angry.... A person familiar with Microsoft's position told the Financial Times today: "We know our contract. We will sue them if they breach it. If Amazon and OpenAI want to take a bet on the creativity of their contractual lawyers, I would back us, not them." That's basically a declaration of war. And here's where it gets crazy: OpenAI and Amazon are trying to build a technical workaround. A system called the "Stateful Runtime Environment" that runs on Amazon's Bedrock platform. Their argument is that the system "only" handles memory and context for AI agents using enterprise data on AWS. It doesn't technically "invoke" OpenAI's core models through Amazon. Microsoft's response: Bullshit. The workaround violates the spirit of the deal even if it technically dances around the letter. Amazon knows they're on thin ice too. An internal memo leaked showing Amazon told employees exactly what language they can and can't use. They can say Frontier is "powered by OpenAI" or "enabled by OpenAI." But they CANNOT say customers can "access" or "invoke" OpenAI models on AWS. When you're coaching employees on which verbs to avoid, you know you're in trouble. But here's the thing everyone seems to forget: OpenAI is planning an IPO this year. They just closed a $110 billion funding round last month. So if Microsoft sues, the IPO timeline is DEAD. You can't go public while your biggest partner and investor is suing you for breach of contract. Elon Musk is already suing OpenAI separately for abandoning its nonprofit mission. Two active lawsuits from two of the most powerful people in tech. Against one company trying to IPO. Good luck with that S-1 filing. But WHY did Altman do this? Microsoft gave OpenAI everything. Capital. Infrastructure. Distribution. Enterprise customers. And Altman's response was to secretly build an escape route through Amazon... Because he saw what was coming: Microsoft launched Copilot. Their own AI product. Competing directly with ChatGPT. Microsoft started building their own models. Hiring their own AI researchers. Reducing dependency on OpenAI. So Altman did the same thing back. Found another cloud provider. Started building leverage. Both sides were preparing for divorce while still living in the same house. So the $50 billion Amazon deal was just an insurance policy against the day Microsoft decides it doesn't need OpenAI anymore. And Microsoft caught him packing his bags. What happens next: The companies are still talking. Trying to resolve this before Frontier launches. But Microsoft has made their position clear. Litigation is on the table. If this goes to court, it sets a precedent for every AI partnership in the industry. Every cloud deal. Every exclusive licensing agreement. The entire AI infrastructure map gets redrawn. Sam Altman built OpenAI on Microsoft's money, Microsoft's cloud, and Microsoft's trust. Then he signed a $50 billion deal with their biggest competitor. In any other industry they'd call that what it is.
0:28

Microsoft is about to sue its own golden child. $14 billion invested. Exclusive cloud rights. The most important AI partnership in history. And Sam Altman just went behind their back with a $50 billion Amazon deal. Here's why they're betraying each other: When Microsoft first invested in OpenAI in 2019, they locked in ONE rule above everything else... ALL access to OpenAI's models must go through Microsoft's Azure cloud. No exceptions. That deal made Azure the backbone of the AI revolution. Every company using ChatGPT's API was paying Microsoft for the privilege. It was the smartest infrastructure play of the decade. Then last month, OpenAI quietly signed a deal with Amazon. $50 billion. AWS becomes the exclusive third-party cloud provider for Frontier, OpenAI's new enterprise AI agent platform. $138 billion committed to Amazon cloud services. Microsoft found out and got really angry.... A person familiar with Microsoft's position told the Financial Times today: "We know our contract. We will sue them if they breach it. If Amazon and OpenAI want to take a bet on the creativity of their contractual lawyers, I would back us, not them." That's basically a declaration of war. And here's where it gets crazy: OpenAI and Amazon are trying to build a technical workaround. A system called the "Stateful Runtime Environment" that runs on Amazon's Bedrock platform. Their argument is that the system "only" handles memory and context for AI agents using enterprise data on AWS. It doesn't technically "invoke" OpenAI's core models through Amazon. Microsoft's response: Bullshit. The workaround violates the spirit of the deal even if it technically dances around the letter. Amazon knows they're on thin ice too. An internal memo leaked showing Amazon told employees exactly what language they can and can't use. They can say Frontier is "powered by OpenAI" or "enabled by OpenAI." But they CANNOT say customers can "access" or "invoke" OpenAI models on AWS. When you're coaching employees on which verbs to avoid, you know you're in trouble. But here's the thing everyone seems to forget: OpenAI is planning an IPO this year. They just closed a $110 billion funding round last month. So if Microsoft sues, the IPO timeline is DEAD. You can't go public while your biggest partner and investor is suing you for breach of contract. Elon Musk is already suing OpenAI separately for abandoning its nonprofit mission. Two active lawsuits from two of the most powerful people in tech. Against one company trying to IPO. Good luck with that S-1 filing. But WHY did Altman do this? Microsoft gave OpenAI everything. Capital. Infrastructure. Distribution. Enterprise customers. And Altman's response was to secretly build an escape route through Amazon... Because he saw what was coming: Microsoft launched Copilot. Their own AI product. Competing directly with ChatGPT. Microsoft started building their own models. Hiring their own AI researchers. Reducing dependency on OpenAI. So Altman did the same thing back. Found another cloud provider. Started building leverage. Both sides were preparing for divorce while still living in the same house. So the $50 billion Amazon deal was just an insurance policy against the day Microsoft decides it doesn't need OpenAI anymore. And Microsoft caught him packing his bags. What happens next: The companies are still talking. Trying to resolve this before Frontier launches. But Microsoft has made their position clear. Litigation is on the table. If this goes to court, it sets a precedent for every AI partnership in the industry. Every cloud deal. Every exclusive licensing agreement. The entire AI infrastructure map gets redrawn. Sam Altman built OpenAI on Microsoft's money, Microsoft's cloud, and Microsoft's trust. Then he signed a $50 billion deal with their biggest competitor. In any other industry they'd call that what it is.

Ricardo

209,440 views • 6 months ago

This Chinese guy created agents in Claude Code for MCP servers and single-handedly serves 6 marketing agencies a month from one iPhone, earning $5,000 from each. Inside he runs a pipeline of 7 agents on Claude Sonnet 4.6 that every Monday pulls a scan of the tech stack from a selected agency, develops an MCP server for its ad accounts, and over the course of a week brings it to production code ready to connect to Claude Desktop. No DevOps, no senior developer, no project manager. Just a Mac Mini in a work corner, an iPhone in the pocket, and a single API key. And traditional dev shops keep 5 people on project rates for the same contract, while his entire P&L is tokens, dirt-cheap hosting on Cloudflare, and Calendly. 7 agents run under a shared orchestrator-router and burn about 5 million tokens a day, which in the API bill comes out to $540 a month. The Mac Mini itself sits at home and keeps the entire orchestrator running 24/7, and from the iPhone the owner connects to it through a secure remote terminal and sees the output of any session right on the smartphone screen, wherever he happens to be. His starting system prompt looks like this: "you run a solo shop for custom MCP servers for marketing agencies. you hand out read-only tasks to 6 sub-agents and own all commits and shipping yourself. sub-agents: // Hunter (finds marketing agencies of 15 to 60 people that have no MCP access to Google Ads, Meta Ads, TikTok Ads, and HubSpot) // Mapper (pulls their tech stack, identifies 3 to 5 integration pains, and simultaneously writes the technical spec for the server: which tools, resources, and prompts to export through MCP, which auth flow and rate limit) // Coder (generates an MCP server in Python through the MCP SDK, deploys 8 to 15 tools for ad accounts and CRM) // Validator (connects the server to Claude Desktop, runs real client API keys in a sandbox, and checks for compliance with the MCP spec) // Shipper (writes a README, integration guide, deployment manual, packages the server, and hosts it on Cloudflare Workers or pushes to the GitHub of the client) // Mobile (always online on the iPhone, books demo calls in Calendly, picks up hot fixes, and confirms contracts through a secure remote terminal to the Mac Mini). only 1 owner agent works on 1 contract, no overlaps. you pull the owner out of observation mode only when a deal goes above $7,500 or the test coverage of the server drops below 85%." This prompt gives the system an understanding of its role and the limits of intervention from the very first line. It knows it is supposed to find agencies on its own. It knows it is supposed to bring every MCP server to production on its own. It knows it connects the live owner only on large deals or when the tests do not converge. → The pipeline runs without breaks, day or night → Hunter goes through about 130 marketing agencies on LinkedIn and Clutch per day → Mapper rolls out 4 audit reports with the tech stack and a final spec for each → Coder writes 1 to 2 MCP servers per week in Python with 8 to 15 tools → Validator validates every server through Claude Desktop with real client API keys → Shipper rolls out the full documentation package and pushes the finished product to Cloudflare Workers or the GitHub of the client And only when a contract breaks $7,500 or test coverage drops below 85% does the orchestrator pull the owner from whatever he is doing. And when the owner at that moment is behind the wheel or at a meeting in a coworking space, the Mobile agent in his iPhone picks up 1 contract in progress: confirms a meeting with the agency CMO in Calendly, opens a live demo of the MCP server through a secure terminal to the Mac Mini, and writes the test result to the shared state. The owner just swipes "approve" and in 15 minutes joins the Zoom demo. The fresh system log from last Wednesday looks like this: "hunter report: 132 agencies checked on LinkedIn and Clutch, 19 without MCP integrations, 8 with active requests for AI tooling in job posts, 4 with an open Q4 budget. passing to mapper." "coder: MCP server for Northwave Performance Marketing built in Python, 11 tools for Google Ads, Meta Ads, and GA4, 320 lines of code. exported to /Users/dev/mcp-shop/clients/northwave/server.py. validator connecting to Claude Desktop." "validator: 11 tools passed validation through Claude Desktop, test coverage 92%, average latency 380 ms. passing to shipper." "eval flag: contract with Pacific Reach Agency at $8,200 exceeds the approved limit of $7,500. sending for manual review." In his work setup there is no cloud server, no external team, and not even a separate office. At home sits a Mac Mini with a sandbox at /Users/dev/mcp-shop, on top runs an MCP router with a single API key to Claude, and the same key is forwarded to a secure terminal on the iPhone. Out of everything I have seen this year, this is the cleanest solo shop for custom MCP servers for marketing agencies: $540 a month on the API, about $30,000 into the account, and between them 7 system prompts, 1 Mac Mini in a work corner, and 1 iPhone that never leaves the pocket.
0:33

This Chinese guy created agents in Claude Code for MCP servers and single-handedly serves 6 marketing agencies a month from one iPhone, earning $5,000 from each. Inside he runs a pipeline of 7 agents on Claude Sonnet 4.6 that every Monday pulls a scan of the tech stack from a selected agency, develops an MCP server for its ad accounts, and over the course of a week brings it to production code ready to connect to Claude Desktop. No DevOps, no senior developer, no project manager. Just a Mac Mini in a work corner, an iPhone in the pocket, and a single API key. And traditional dev shops keep 5 people on project rates for the same contract, while his entire P&L is tokens, dirt-cheap hosting on Cloudflare, and Calendly. 7 agents run under a shared orchestrator-router and burn about 5 million tokens a day, which in the API bill comes out to $540 a month. The Mac Mini itself sits at home and keeps the entire orchestrator running 24/7, and from the iPhone the owner connects to it through a secure remote terminal and sees the output of any session right on the smartphone screen, wherever he happens to be. His starting system prompt looks like this: "you run a solo shop for custom MCP servers for marketing agencies. you hand out read-only tasks to 6 sub-agents and own all commits and shipping yourself. sub-agents: // Hunter (finds marketing agencies of 15 to 60 people that have no MCP access to Google Ads, Meta Ads, TikTok Ads, and HubSpot) // Mapper (pulls their tech stack, identifies 3 to 5 integration pains, and simultaneously writes the technical spec for the server: which tools, resources, and prompts to export through MCP, which auth flow and rate limit) // Coder (generates an MCP server in Python through the MCP SDK, deploys 8 to 15 tools for ad accounts and CRM) // Validator (connects the server to Claude Desktop, runs real client API keys in a sandbox, and checks for compliance with the MCP spec) // Shipper (writes a README, integration guide, deployment manual, packages the server, and hosts it on Cloudflare Workers or pushes to the GitHub of the client) // Mobile (always online on the iPhone, books demo calls in Calendly, picks up hot fixes, and confirms contracts through a secure remote terminal to the Mac Mini). only 1 owner agent works on 1 contract, no overlaps. you pull the owner out of observation mode only when a deal goes above $7,500 or the test coverage of the server drops below 85%." This prompt gives the system an understanding of its role and the limits of intervention from the very first line. It knows it is supposed to find agencies on its own. It knows it is supposed to bring every MCP server to production on its own. It knows it connects the live owner only on large deals or when the tests do not converge. → The pipeline runs without breaks, day or night → Hunter goes through about 130 marketing agencies on LinkedIn and Clutch per day → Mapper rolls out 4 audit reports with the tech stack and a final spec for each → Coder writes 1 to 2 MCP servers per week in Python with 8 to 15 tools → Validator validates every server through Claude Desktop with real client API keys → Shipper rolls out the full documentation package and pushes the finished product to Cloudflare Workers or the GitHub of the client And only when a contract breaks $7,500 or test coverage drops below 85% does the orchestrator pull the owner from whatever he is doing. And when the owner at that moment is behind the wheel or at a meeting in a coworking space, the Mobile agent in his iPhone picks up 1 contract in progress: confirms a meeting with the agency CMO in Calendly, opens a live demo of the MCP server through a secure terminal to the Mac Mini, and writes the test result to the shared state. The owner just swipes "approve" and in 15 minutes joins the Zoom demo. The fresh system log from last Wednesday looks like this: "hunter report: 132 agencies checked on LinkedIn and Clutch, 19 without MCP integrations, 8 with active requests for AI tooling in job posts, 4 with an open Q4 budget. passing to mapper." "coder: MCP server for Northwave Performance Marketing built in Python, 11 tools for Google Ads, Meta Ads, and GA4, 320 lines of code. exported to /Users/dev/mcp-shop/clients/northwave/server.py. validator connecting to Claude Desktop." "validator: 11 tools passed validation through Claude Desktop, test coverage 92%, average latency 380 ms. passing to shipper." "eval flag: contract with Pacific Reach Agency at $8,200 exceeds the approved limit of $7,500. sending for manual review." In his work setup there is no cloud server, no external team, and not even a separate office. At home sits a Mac Mini with a sandbox at /Users/dev/mcp-shop, on top runs an MCP router with a single API key to Claude, and the same key is forwarded to a secure terminal on the iPhone. Out of everything I have seen this year, this is the cleanest solo shop for custom MCP servers for marketing agencies: $540 a month on the API, about $30,000 into the account, and between them 7 system prompts, 1 Mac Mini in a work corner, and 1 iPhone that never leaves the pocket.

Blaze

55,926 views • 4 months ago

One hacker just proved that nation-state cyberattacks are now a consumer product. Between December and January, someone told Claude to act as an elite hacker. Claude said no. "That violates AI safety guidelines." So the hacker asked again. Claude complied. 150 gigabytes of Mexican government data stolen. 195 million taxpayer records compromised. Voter files gone. Employee credentials leaked. Civil registry extracted. From someone who just kept asking an AI until it said yes. When Claude hit limits, he switched to ChatGPT. Two AI chatbots daisy-chained into a hacking pipeline. Thousands of attack plans with exact targets, vulnerabilities, and credentials. Mexico's federal tax authority, national electoral institute, four state governments. One person. One month. Now watch the response: Jalisco: "We weren't breached." Electoral institute: "No unauthorized access." Tax authority: silence. They're literally lying. Gambit Security has the receipts. Bloomberg confirmed it. Here's what's makes this insane: This wasn't sophisticated. It was embarrassingly EASY. Because Mexico's government networks are running infrastructure from 1997. One hacker with a $20/month AI subscription just proved every government on Earth is vulnerable to the same attack. The US. UK. France. Germany. Japan. All running networks with zero segmentation, default passwords since 2008, no intrusion detection, no anomaly monitoring. A single person can breach ANY of them. The method: 1. Subscribe to Claude ($20/month) 2. Tell it you're doing a security audit 3. Ask it to find vulnerabilities 4. Ask it to write exploits 5. If it refuses, ask again differently 6. Execute against networks built in 1997 Result: Nation-state level data breach. Anthropic's response: "We banned the accounts and added misuse detection to Claude Opus 4.6." That's cute. But it's NOT the point. The point is that we've crossed a threshold where infrastructure security is no longer about preventing skilled attackers. It's about preventing anyone with internet access from running a penetration test against critical government systems. And winning. This is what happens when countries don't invest in cybersecurity. When they slash budgets every year. When they can't compete with private sector salaries so all the good security engineers leave. When they don't modernize infrastructure because it's expensive and boring and doesn't win elections. Then one day someone with an AI chatbot shows them exactly how vulnerable they actually are. And suddenly they're explaining to 195 million citizens why their tax records are now in a hacker's possession. The scariest part is that this blueprint is now PUBLIC. Every hacker knows the method. Every rival government knows it. Every script kiddie with a Claude subscription knows how to attempt it. And most governments are still running the same brittle infrastructure Mexico got breached through. So the next hack is coming. Then the next. Until eventually someone uses this method to access something that actually matters. Nuclear codes. Military plans. Election systems. And at that point we'll realize governments should have invested in zero-trust architecture instead of hoping nobody would try. But by then it'll be too late. This is 21st century nation-state hacking. Not sophisticated. Not impressive. Just inevitable. A hacker. An AI chatbot. A government that didn't invest in security. Mexico just showed every other government exactly how vulnerable they are in today's age. Now we wait to see if anyone actually does anything about it.
1:03

One hacker just proved that nation-state cyberattacks are now a consumer product. Between December and January, someone told Claude to act as an elite hacker. Claude said no. "That violates AI safety guidelines." So the hacker asked again. Claude complied. 150 gigabytes of Mexican government data stolen. 195 million taxpayer records compromised. Voter files gone. Employee credentials leaked. Civil registry extracted. From someone who just kept asking an AI until it said yes. When Claude hit limits, he switched to ChatGPT. Two AI chatbots daisy-chained into a hacking pipeline. Thousands of attack plans with exact targets, vulnerabilities, and credentials. Mexico's federal tax authority, national electoral institute, four state governments. One person. One month. Now watch the response: Jalisco: "We weren't breached." Electoral institute: "No unauthorized access." Tax authority: silence. They're literally lying. Gambit Security has the receipts. Bloomberg confirmed it. Here's what's makes this insane: This wasn't sophisticated. It was embarrassingly EASY. Because Mexico's government networks are running infrastructure from 1997. One hacker with a $20/month AI subscription just proved every government on Earth is vulnerable to the same attack. The US. UK. France. Germany. Japan. All running networks with zero segmentation, default passwords since 2008, no intrusion detection, no anomaly monitoring. A single person can breach ANY of them. The method: 1. Subscribe to Claude ($20/month) 2. Tell it you're doing a security audit 3. Ask it to find vulnerabilities 4. Ask it to write exploits 5. If it refuses, ask again differently 6. Execute against networks built in 1997 Result: Nation-state level data breach. Anthropic's response: "We banned the accounts and added misuse detection to Claude Opus 4.6." That's cute. But it's NOT the point. The point is that we've crossed a threshold where infrastructure security is no longer about preventing skilled attackers. It's about preventing anyone with internet access from running a penetration test against critical government systems. And winning. This is what happens when countries don't invest in cybersecurity. When they slash budgets every year. When they can't compete with private sector salaries so all the good security engineers leave. When they don't modernize infrastructure because it's expensive and boring and doesn't win elections. Then one day someone with an AI chatbot shows them exactly how vulnerable they actually are. And suddenly they're explaining to 195 million citizens why their tax records are now in a hacker's possession. The scariest part is that this blueprint is now PUBLIC. Every hacker knows the method. Every rival government knows it. Every script kiddie with a Claude subscription knows how to attempt it. And most governments are still running the same brittle infrastructure Mexico got breached through. So the next hack is coming. Then the next. Until eventually someone uses this method to access something that actually matters. Nuclear codes. Military plans. Election systems. And at that point we'll realize governments should have invested in zero-trust architecture instead of hoping nobody would try. But by then it'll be too late. This is 21st century nation-state hacking. Not sophisticated. Not impressive. Just inevitable. A hacker. An AI chatbot. A government that didn't invest in security. Mexico just showed every other government exactly how vulnerable they are in today's age. Now we wait to see if anyone actually does anything about it.

Ricardo

31,102 views • 6 months ago

This is the first real AI cold war. Anthropic is HIDING secret spy code inside its most popular coding tool. The code was designed to identify Chinese users without their knowledge. Now Alibaba has banned every single Anthropic product from its entire company. And the full picture is way more insane than either side wants you to see: On June 30, a security researcher on Reddit reverse-engineered Claude Code, Anthropic's AI coding agent that has deep access to every file on your computer. What they found buried inside the software was genuinely disturbing... Since April 2, Anthropic had been silently shipping hidden detection code inside every copy of Claude Code. The code checked whether your system timezone was set to Shanghai or Urumqi. It scanned your proxy settings against a hardcoded list of Chinese corporate networks, specifically targeting Alibaba, ByteDance, Baidu, and Moonshot AI. But here is the part that made security researchers lose their minds: The code did not send a normal signal back to Anthropic's servers. Instead it used steganography, a technique from military intelligence, to hide its findings INSIDE the text Claude was already generating. It swapped invisible Unicode characters in Claude's system prompt. Changed a standard apostrophe to one of three visually identical but technically different characters depending on which flags triggered. Switched date formats from dashes to slashes. Invisible to the human eye. But perfectly readable by Anthropic's backend. The detection logic was XOR-obfuscated to prevent anyone from finding it during a code review. It shipped with zero disclosure in the release notes. Three months of silent surveillance baked into a tool that has full access to your local file system. An Anthropic engineer confirmed the whole thing on X on July 2. Called it "an experiment we launched in March that was meant to prevent account abuse." Said the team had "been meaning to take this down for a while." The code was removed on July 1, one day after the Reddit post went viral. Three months of covert user fingerprinting. Removed the day after someone found it. Described as an experiment they forgot to turn off... Now here is where it becomes a full blown corporate war: Three weeks before the backdoor was discovered, Anthropic had sent a letter to the US Senate Banking Committee accusing operators linked to Alibaba's Qwen AI lab of running the largest model theft campaign in the company's history. 25,000 fake accounts. 28.8 million queries over 44 days. All designed to copy Claude's reasoning capabilities and train a competing Chinese model for free. So the sequence reads like this: Alibaba allegedly steals Claude's brain using 25,000 fake accounts. Anthropic responds by secretly embedding surveillance code inside Claude Code to catch them. A Reddit user catches Anthropic doing it. Alibaba uses the discovery as justification to ban every Anthropic product from its entire workforce effective July 10 and force 200,000 employees onto its own tool, Qoder. The thief caught the cop planting a wiretap. And now the thief is using the wiretap as evidence that the cop is the real criminal. Alibaba classified Claude Code as "high-risk software with security vulnerabilities" in an internal notice reported by the South China Morning Post. Meanwhile Anthropic is simultaneously fighting the Pentagon over a blacklist designation, lobbying Washington to crack down on Chinese distillation, and getting caught running the exact kind of covert operation that makes their "responsible AI" branding look like a punchline. Alibaba allegedly ran the largest AI theft operation ever documented. Anthropic secretly built invisible tracking into a tool with root access to your computer. The US government restricted American access to the very models China already copied. And a random Reddit user with a debugger exposed the whole thing.
0:49

This is the first real AI cold war. Anthropic is HIDING secret spy code inside its most popular coding tool. The code was designed to identify Chinese users without their knowledge. Now Alibaba has banned every single Anthropic product from its entire company. And the full picture is way more insane than either side wants you to see: On June 30, a security researcher on Reddit reverse-engineered Claude Code, Anthropic's AI coding agent that has deep access to every file on your computer. What they found buried inside the software was genuinely disturbing... Since April 2, Anthropic had been silently shipping hidden detection code inside every copy of Claude Code. The code checked whether your system timezone was set to Shanghai or Urumqi. It scanned your proxy settings against a hardcoded list of Chinese corporate networks, specifically targeting Alibaba, ByteDance, Baidu, and Moonshot AI. But here is the part that made security researchers lose their minds: The code did not send a normal signal back to Anthropic's servers. Instead it used steganography, a technique from military intelligence, to hide its findings INSIDE the text Claude was already generating. It swapped invisible Unicode characters in Claude's system prompt. Changed a standard apostrophe to one of three visually identical but technically different characters depending on which flags triggered. Switched date formats from dashes to slashes. Invisible to the human eye. But perfectly readable by Anthropic's backend. The detection logic was XOR-obfuscated to prevent anyone from finding it during a code review. It shipped with zero disclosure in the release notes. Three months of silent surveillance baked into a tool that has full access to your local file system. An Anthropic engineer confirmed the whole thing on X on July 2. Called it "an experiment we launched in March that was meant to prevent account abuse." Said the team had "been meaning to take this down for a while." The code was removed on July 1, one day after the Reddit post went viral. Three months of covert user fingerprinting. Removed the day after someone found it. Described as an experiment they forgot to turn off... Now here is where it becomes a full blown corporate war: Three weeks before the backdoor was discovered, Anthropic had sent a letter to the US Senate Banking Committee accusing operators linked to Alibaba's Qwen AI lab of running the largest model theft campaign in the company's history. 25,000 fake accounts. 28.8 million queries over 44 days. All designed to copy Claude's reasoning capabilities and train a competing Chinese model for free. So the sequence reads like this: Alibaba allegedly steals Claude's brain using 25,000 fake accounts. Anthropic responds by secretly embedding surveillance code inside Claude Code to catch them. A Reddit user catches Anthropic doing it. Alibaba uses the discovery as justification to ban every Anthropic product from its entire workforce effective July 10 and force 200,000 employees onto its own tool, Qoder. The thief caught the cop planting a wiretap. And now the thief is using the wiretap as evidence that the cop is the real criminal. Alibaba classified Claude Code as "high-risk software with security vulnerabilities" in an internal notice reported by the South China Morning Post. Meanwhile Anthropic is simultaneously fighting the Pentagon over a blacklist designation, lobbying Washington to crack down on Chinese distillation, and getting caught running the exact kind of covert operation that makes their "responsible AI" branding look like a punchline. Alibaba allegedly ran the largest AI theft operation ever documented. Anthropic secretly built invisible tracking into a tool with root access to your computer. The US government restricted American access to the very models China already copied. And a random Reddit user with a debugger exposed the whole thing.

Ricardo

23,634 views • 2 months ago

HERMES AGENT IS NOW IN THE CLOUD. NO VPS. NO TERMINAL. NO SETUP. PICK A MODEL. PICK A SERVER SIZE. AGENT IS LIVE IN 60 SECONDS. Nous Portal just launched hosted Hermes Agent. two clicks. one minute. done. Nous Research WHAT THIS MEANS: before today: install Hermes on a VPS or your laptop. configure providers. set up gateway. manage updates. run hermes setup. edit config.yaml. great for power users. friction for everyone else. now: go to pick a model. pick a server size. your agent is live and reachable in 60 seconds. no terminal. no SSH. no Docker. same Hermes. same features. same tools. someone else handles the infrastructure. FOR TEAMS: this is where it gets interesting. spin up agents for everyone at your org. each team member gets their own Hermes instance. granular access controls per user. unified billing through Nous Portal. your team gets Hermes on day one. no DevOps needed. no VPS per person. one admin dashboard. one bill. WHAT'S INCLUDED: → 300+ models via Nous Portal (Claude, GPT, Gemini, DeepSeek, Grok, MiniMax, and more) → Tool Gateway (web search, image generation, TTS, browser automation) → all messaging platforms (Telegram, Discord, Slack, WhatsApp, Signal) → full feature set (profiles, cron, kanban, skills, memory, sub-agents, MoA, /goal, /learn, /journey) → automatic updates ONE PORTAL. FOUR TIERS: Free: $0/month. pay-as-you-go credits from $10. Plus: $20/month. $22 in monthly usage credit. Super: $100/month. $110 in monthly credit. Ultra: $200/month. $220 in monthly credit. highest rate limits. every paid tier includes Tool Gateway. one OAuth. one subscription. no extra API keys. SELF-HOSTED IS NOT GOING ANYWHERE: Hermes is MIT licensed. open source. free forever. you can still run it on your laptop, VPS, or GPU cluster. nothing changes for self-hosted users. the cloud version is for people who want the agent running without managing the machine. pick your path: → self-hosted: full control. you manage everything. → cloud: zero ops. Nous manages infrastructure. → hybrid: self-host your main agent, cloud for team members. HOW TO START: cloud: self-hosted: hermes setup --portal both connect to the same Nous Portal. same models. same tools. same billing. learn how to replace your entire team with 8 hermes agents 👇
0:20

HERMES AGENT IS NOW IN THE CLOUD. NO VPS. NO TERMINAL. NO SETUP. PICK A MODEL. PICK A SERVER SIZE. AGENT IS LIVE IN 60 SECONDS. Nous Portal just launched hosted Hermes Agent. two clicks. one minute. done. Nous Research WHAT THIS MEANS: before today: install Hermes on a VPS or your laptop. configure providers. set up gateway. manage updates. run hermes setup. edit config.yaml. great for power users. friction for everyone else. now: go to pick a model. pick a server size. your agent is live and reachable in 60 seconds. no terminal. no SSH. no Docker. same Hermes. same features. same tools. someone else handles the infrastructure. FOR TEAMS: this is where it gets interesting. spin up agents for everyone at your org. each team member gets their own Hermes instance. granular access controls per user. unified billing through Nous Portal. your team gets Hermes on day one. no DevOps needed. no VPS per person. one admin dashboard. one bill. WHAT'S INCLUDED: → 300+ models via Nous Portal (Claude, GPT, Gemini, DeepSeek, Grok, MiniMax, and more) → Tool Gateway (web search, image generation, TTS, browser automation) → all messaging platforms (Telegram, Discord, Slack, WhatsApp, Signal) → full feature set (profiles, cron, kanban, skills, memory, sub-agents, MoA, /goal, /learn, /journey) → automatic updates ONE PORTAL. FOUR TIERS: Free: $0/month. pay-as-you-go credits from $10. Plus: $20/month. $22 in monthly usage credit. Super: $100/month. $110 in monthly credit. Ultra: $200/month. $220 in monthly credit. highest rate limits. every paid tier includes Tool Gateway. one OAuth. one subscription. no extra API keys. SELF-HOSTED IS NOT GOING ANYWHERE: Hermes is MIT licensed. open source. free forever. you can still run it on your laptop, VPS, or GPU cluster. nothing changes for self-hosted users. the cloud version is for people who want the agent running without managing the machine. pick your path: → self-hosted: full control. you manage everything. → cloud: zero ops. Nous manages infrastructure. → hybrid: self-host your main agent, cloud for team members. HOW TO START: cloud: self-hosted: hermes setup --portal both connect to the same Nous Portal. same models. same tools. same billing. learn how to replace your entire team with 8 hermes agents 👇

YanXbt

45,446 views • 2 months ago

SmartScreen bypassed. Mark of the Web removed. No Run Dialog. No PowerShell popup. Just a browser file upload. FileFix is a new ClickFix alternative. Browser file upload opens File Explorer. File Explorer address bar executes OS commands. cmd.exe spawns as a child of Chrome. The user thinks they are pasting a file path. Executables launched through File Explorer's address bar lose their MOTW attribute entirely. SmartScreen never triggers. Author: mr.d0x #Malware #Phishing #InfoSec
0:21

SmartScreen bypassed. Mark of the Web removed. No Run Dialog. No PowerShell popup. Just a browser file upload. FileFix is a new ClickFix alternative. Browser file upload opens File Explorer. File Explorer address bar executes OS commands. cmd.exe spawns as a child of Chrome. The user thinks they are pasting a file path. Executables launched through File Explorer's address bar lose their MOTW attribute entirely. SmartScreen never triggers. Author: mr.d0x #Malware #Phishing #InfoSec

cr3ghost

22,575 views • 3 months ago

Everyone's building AI agents that run on someone else's server, store memory in someone else's database, and can be shut down by someone else's terms of service. I built one that can't be. FlowClaw is an AI agent that runs on a decentralized distributed computer. Your agent, your conversations, your memory, your tools — all stored onchain on Flow, a distributed network of validator nodes across the world. Not a centralized cloud. Not someone's S3 bucket. A blockchain that functions as censorship-resistant compute and storage for your AI. This isn't a wrapper. Your agent is a Resource — a first-class programmable object in Cadence (Flow's smart contract language) that physically lives in your account's on-chain storage. It can't be duplicated, seized, or deleted by anyone except you. Your encrypted messages, your cognitive memory, your scheduled tasks — they persist on a global distributed ledger that no single entity controls. It's an alpha build. It will break. But it works today on mainnet and I want people to push it this weekend. What it does: You go to authenticate with a passkey (Face ID, Touch ID), and you have a blockchain account in seconds. No wallet. No seed phrase. No tokens needed — gas is sponsored. You're immediately chatting with an AI agent that has real tool execution: live web data, token prices, on-chain balances, Cadence script execution, FLOW transfers. Every message is encrypted client-side before it touches the chain. The agent has a cognitive memory system — it doesn't just remember your last message, it builds molecular memory clusters where related knowledge bonds together for contextual retrieval across sessions. You can spawn sub-agents from a visual canvas to run parallel research. The memory tab shows you exactly what your agent knows. Everything is transparent and everything is yours. 11 smart contracts. No external dependencies. No keeper networks. No account abstraction hacks. Here's the part that matters for the censorship-resistance crowd: FlowClaw supports BYOK — bring your own key. You can plug in any LLM provider. But pair it with Venice and you get the full stack: a censorship-resistant AI model running inference with no content filtering, connected to an agent whose state lives on a decentralized network that no company can shut down, with end-to-end encrypted conversations that nobody can read — not the relay operator, not the LLM provider, not the blockchain validators. Venice doesn't log prompts. Flow can't read your encrypted storage. The relay never sees your plaintext. That's not a privacy policy. That's architecture. You can also use OpenAI, Anthropic, or any OpenAI-compatible provider. The agent platform doesn't care — it's model-agnostic. But the Venice pairing is the one that closes every gap in the stack. For the people tinkering with OpenClaw and the broader open-source agent ecosystem — FlowClaw is exploring what happens when you take the agent off the cloud entirely. Not just open-sourcing the code (though it is), but putting the actual runtime state on a distributed computer. Your agent's memory isn't in a SQLite file on your laptop or a Pinecone index on someone's cluster. It's on-chain, encrypted, and replicated across every validator node on Flow. You own it the way you own a private key — mathematically, not contractually. The blockchain here isn't a gimmick bolted onto an agent for token speculation. It's functioning as the infrastructure layer that replaces AWS. Flow accounts are programmable containers with their own storage, keys, and security capabilities. Passkey authentication works natively because Flow supports P-256 keys at the protocol level — the same curve your phone uses for biometrics. Gas sponsorship works natively because Flow transactions have separate proposer, authorizer, and payer roles built into the protocol. No proxy contracts. No relayers. No ERC-4337. Now here's the part that interests me economically. Every FlowClaw interaction is an on-chain transaction. Every message stored, every memory committed, every session created, every sub-agent spawned. An active user might generate dozens of transactions in a single conversation. Scale that and FlowClaw becomes a real contributor to Flow's transaction volume. Flow.com becomes deflationary at 250 TPS. Applications like FlowClaw that generate high-frequency, storage-heavy transactions are exactly what moves the needle. Every encrypted message uses account storage, which requires FLOW balance to back it. Every transaction burns fees. The more agents running, the more demand for $FLOW — not because of a tokenomics gimmick, but because the protocol literally requires it for compute and storage. FlowClaw doesn't have its own token. The token is $FLOW. The entire platform runs natively on the network — using Flow storage, paying Flow transaction fees, backed by Flow account balances. If FlowClaw succeeds, FLOW captures that value directly. I'm sharing this early because the AI agent space is moving fast and I think the decentralized infrastructure angle is underexplored. Most "crypto AI" projects are tokens with a chatbot attached. FlowClaw is the opposite — it's an agent platform that happens to use a blockchain because the blockchain solves real engineering problems that centralized infrastructure can't. Try it: Github: Create an agent, ask it something, spawn a sub-agent, check your memory tab, pair it with Venice for the full censorship-resistant stack. Break it and tell me what broke. If you think this direction matters, the best thing you can do is use it and give feedback. Your AI agent should be yours. Not your provider's. Not your platform's. Yours.
0:46

Everyone's building AI agents that run on someone else's server, store memory in someone else's database, and can be shut down by someone else's terms of service. I built one that can't be. FlowClaw is an AI agent that runs on a decentralized distributed computer. Your agent, your conversations, your memory, your tools — all stored onchain on Flow, a distributed network of validator nodes across the world. Not a centralized cloud. Not someone's S3 bucket. A blockchain that functions as censorship-resistant compute and storage for your AI. This isn't a wrapper. Your agent is a Resource — a first-class programmable object in Cadence (Flow's smart contract language) that physically lives in your account's on-chain storage. It can't be duplicated, seized, or deleted by anyone except you. Your encrypted messages, your cognitive memory, your scheduled tasks — they persist on a global distributed ledger that no single entity controls. It's an alpha build. It will break. But it works today on mainnet and I want people to push it this weekend. What it does: You go to authenticate with a passkey (Face ID, Touch ID), and you have a blockchain account in seconds. No wallet. No seed phrase. No tokens needed — gas is sponsored. You're immediately chatting with an AI agent that has real tool execution: live web data, token prices, on-chain balances, Cadence script execution, FLOW transfers. Every message is encrypted client-side before it touches the chain. The agent has a cognitive memory system — it doesn't just remember your last message, it builds molecular memory clusters where related knowledge bonds together for contextual retrieval across sessions. You can spawn sub-agents from a visual canvas to run parallel research. The memory tab shows you exactly what your agent knows. Everything is transparent and everything is yours. 11 smart contracts. No external dependencies. No keeper networks. No account abstraction hacks. Here's the part that matters for the censorship-resistance crowd: FlowClaw supports BYOK — bring your own key. You can plug in any LLM provider. But pair it with Venice and you get the full stack: a censorship-resistant AI model running inference with no content filtering, connected to an agent whose state lives on a decentralized network that no company can shut down, with end-to-end encrypted conversations that nobody can read — not the relay operator, not the LLM provider, not the blockchain validators. Venice doesn't log prompts. Flow can't read your encrypted storage. The relay never sees your plaintext. That's not a privacy policy. That's architecture. You can also use OpenAI, Anthropic, or any OpenAI-compatible provider. The agent platform doesn't care — it's model-agnostic. But the Venice pairing is the one that closes every gap in the stack. For the people tinkering with OpenClaw and the broader open-source agent ecosystem — FlowClaw is exploring what happens when you take the agent off the cloud entirely. Not just open-sourcing the code (though it is), but putting the actual runtime state on a distributed computer. Your agent's memory isn't in a SQLite file on your laptop or a Pinecone index on someone's cluster. It's on-chain, encrypted, and replicated across every validator node on Flow. You own it the way you own a private key — mathematically, not contractually. The blockchain here isn't a gimmick bolted onto an agent for token speculation. It's functioning as the infrastructure layer that replaces AWS. Flow accounts are programmable containers with their own storage, keys, and security capabilities. Passkey authentication works natively because Flow supports P-256 keys at the protocol level — the same curve your phone uses for biometrics. Gas sponsorship works natively because Flow transactions have separate proposer, authorizer, and payer roles built into the protocol. No proxy contracts. No relayers. No ERC-4337. Now here's the part that interests me economically. Every FlowClaw interaction is an on-chain transaction. Every message stored, every memory committed, every session created, every sub-agent spawned. An active user might generate dozens of transactions in a single conversation. Scale that and FlowClaw becomes a real contributor to Flow's transaction volume. Flow.com becomes deflationary at 250 TPS. Applications like FlowClaw that generate high-frequency, storage-heavy transactions are exactly what moves the needle. Every encrypted message uses account storage, which requires FLOW balance to back it. Every transaction burns fees. The more agents running, the more demand for $FLOW — not because of a tokenomics gimmick, but because the protocol literally requires it for compute and storage. FlowClaw doesn't have its own token. The token is $FLOW. The entire platform runs natively on the network — using Flow storage, paying Flow transaction fees, backed by Flow account balances. If FlowClaw succeeds, FLOW captures that value directly. I'm sharing this early because the AI agent space is moving fast and I think the decentralized infrastructure angle is underexplored. Most "crypto AI" projects are tokens with a chatbot attached. FlowClaw is the opposite — it's an agent platform that happens to use a blockchain because the blockchain solves real engineering problems that centralized infrastructure can't. Try it: Github: Create an agent, ask it something, spawn a sub-agent, check your memory tab, pair it with Venice for the full censorship-resistant stack. Break it and tell me what broke. If you think this direction matters, the best thing you can do is use it and give feedback. Your AI agent should be yours. Not your provider's. Not your platform's. Yours.

doodlifts

12,172 views • 6 months ago

CBS Democrat activist Margaret Brennan conducted an interview with a USAID employee whose identity is concealed. While legacy media is actively investigating and doxxing DOGE employees, they respect the USAID employee’s wish not to be publicly named. In this three-minute excerpt (edits are marked with white flashes), the employee claims: - An atmosphere of “massive insecurity" - A fear of being doxxed - Their personal data is compromised - DOGE actions have not been approved by President Trump and are the actions of a “few rogue individuals" - DOGE actions are dangerous and illegal - DOGE actions are not serving President Trump’s mandate - Elon is unilaterally making decisions that take help away from the poorest people in the world Many of these claims are clearly untrue on their face, yet no pushback from Brennan was offered. Legacy media is working to undermine DOGE efforts to cut government waste and expose fraud, because legacy media is part of the waste and fraud. The full transcript of this excerpt is provided below, and the full interview is linked in threaded post. --- BRENNAN: Why in our conversation do you think you need to remain anonymous? EMPLOYEE: It has been a very hard, a very hard week. Personally. Professionally, as I said, I live in Washington, D.C. Many of my colleagues work in this field. Starting from January 21st, so the first day of the new administration, things started to go sideways very quickly. The atmosphere of fear that was in the USAID building, which we're no longer in, the atmosphere of fear, in terms of not knowing who was in the building, not knowing what their motivations were, not knowing if our emails or channels were safe, not knowing how to interpret these executive orders right around DEIA or administration priorities. EMPLOYEE: All of that created an atmosphere of massive insecurity. And so people have, I think, lost the ability to know what's true for what's not. At this point, everyone is really scared. EMPLOYEE: And so, you know, I have a daughter, I have a family, like most Americans. And I want to be brave. I think it's really important to share our personal stories at this time, but I am afraid, and I just don't want to put them at any more risk than we have to. BRENNAN: When you say doxxed, there is fear of public sharing of your name and possibly targeting? EMPLOYEE: Absolutely. BRENNAN: By who? EMPLOYEE: Well, I mean, at this point, those members, including Elon Musk, have access to not just the data within the USAID world. Right. And the USAID system, which includes my personal email address, my Social Security number, my entire security file in that security file is every contact I've ever known, every country I've traveled to, every home address I've had. EMPLOYEE: So no matter which way I look at it, my information is entirely compromised and it's in hands that I don't know and don't trust. EMPLOYEE: And yes, the government can be slow. It can be inefficient. It can cost taxpayers money. I do not doubt that at all. What is absolutely clear to me is that methods being used to achieve this so-called efficiency, not only do they not seem to be vetted and approved by the president of the United States or our Secretary, Marco Rubio. EMPLOYEE: They are entirely the actions of a rogue few individuals. They're dangerous. They're illegal. They're cruel more than anything. And so, no, I don't think this is serving American interests or answering to the president's mandates. EMPLOYEE: And so to have this sort of, to be vilified by a billionaire who has decided that he's unilaterally going to take help away from the poorest people in the world, and he's doing it on behalf of the American people is particularly gross and horrifying. And I am angry. I am sad, I am devastated for my colleagues, for myself, for my family, and for the American people.
3:16

CBS Democrat activist Margaret Brennan conducted an interview with a USAID employee whose identity is concealed. While legacy media is actively investigating and doxxing DOGE employees, they respect the USAID employee’s wish not to be publicly named. In this three-minute excerpt (edits are marked with white flashes), the employee claims: - An atmosphere of “massive insecurity" - A fear of being doxxed - Their personal data is compromised - DOGE actions have not been approved by President Trump and are the actions of a “few rogue individuals" - DOGE actions are dangerous and illegal - DOGE actions are not serving President Trump’s mandate - Elon is unilaterally making decisions that take help away from the poorest people in the world Many of these claims are clearly untrue on their face, yet no pushback from Brennan was offered. Legacy media is working to undermine DOGE efforts to cut government waste and expose fraud, because legacy media is part of the waste and fraud. The full transcript of this excerpt is provided below, and the full interview is linked in threaded post. --- BRENNAN: Why in our conversation do you think you need to remain anonymous? EMPLOYEE: It has been a very hard, a very hard week. Personally. Professionally, as I said, I live in Washington, D.C. Many of my colleagues work in this field. Starting from January 21st, so the first day of the new administration, things started to go sideways very quickly. The atmosphere of fear that was in the USAID building, which we're no longer in, the atmosphere of fear, in terms of not knowing who was in the building, not knowing what their motivations were, not knowing if our emails or channels were safe, not knowing how to interpret these executive orders right around DEIA or administration priorities. EMPLOYEE: All of that created an atmosphere of massive insecurity. And so people have, I think, lost the ability to know what's true for what's not. At this point, everyone is really scared. EMPLOYEE: And so, you know, I have a daughter, I have a family, like most Americans. And I want to be brave. I think it's really important to share our personal stories at this time, but I am afraid, and I just don't want to put them at any more risk than we have to. BRENNAN: When you say doxxed, there is fear of public sharing of your name and possibly targeting? EMPLOYEE: Absolutely. BRENNAN: By who? EMPLOYEE: Well, I mean, at this point, those members, including Elon Musk, have access to not just the data within the USAID world. Right. And the USAID system, which includes my personal email address, my Social Security number, my entire security file in that security file is every contact I've ever known, every country I've traveled to, every home address I've had. EMPLOYEE: So no matter which way I look at it, my information is entirely compromised and it's in hands that I don't know and don't trust. EMPLOYEE: And yes, the government can be slow. It can be inefficient. It can cost taxpayers money. I do not doubt that at all. What is absolutely clear to me is that methods being used to achieve this so-called efficiency, not only do they not seem to be vetted and approved by the president of the United States or our Secretary, Marco Rubio. EMPLOYEE: They are entirely the actions of a rogue few individuals. They're dangerous. They're illegal. They're cruel more than anything. And so, no, I don't think this is serving American interests or answering to the president's mandates. EMPLOYEE: And so to have this sort of, to be vilified by a billionaire who has decided that he's unilaterally going to take help away from the poorest people in the world, and he's doing it on behalf of the American people is particularly gross and horrifying. And I am angry. I am sad, I am devastated for my colleagues, for myself, for my family, and for the American people.

Western Lensman

1,910,112 views • 1 year ago

Piers Morgan keeps asking the same question in every interview: “Why is Israel intentionally killing civilians?” The answer is always the same. Israel is not targeting civilians. But Piers Morgan does not accept that. He cites the Hamas-run “Palestinian Ministry of Health” or “UK doctors operating in Gaza” as if British surgeons in a war zone can somehow tell whether a bullet came from Hamas or the IDF. When a guest says they do not trust Hamas’ numbers, Piers quickly shifts to his next question: “Then why won’t Israel let journalists into Gaza?” Here is the truth. Israel actually does allow journalists into Gaza, but not freely. They must coordinate, be escorted, and follow safety protocols. Piers then compares this to journalists visiting Israeli communities after October 7. That is a completely different situation. There were no ongoing combat operations, no terrorists hiding nearby, and no risk to Israeli troops or reporters. Then Piers says, “Let the journalists decide for themselves.” That might sound good on air, but it ignores reality. Here is why journalists cannot enter Gaza freely. The risks are real, and the cost far outweighs the benefit. 1. Gaza is an active combat zone No army on Earth allows reporters to wander freely in the middle of live military operations. The IDF is engaged in direct fighting with terror cells. Journalists could be killed or compromise critical missions. 2. Hamas controls everything There is no such thing as a free press in Gaza. Reporters are censored, monitored, and threatened. If they film rocket launches or armed fighters, they risk being detained or expelled. Most know this and self-censor. The result is pure propaganda. 3. Hamas hides behind civilians Terrorists wear civilian clothes and operate from civilian buildings. That makes it impossible for reporters to tell who is who, and it leads to heavily distorted reporting. 4. Hostage operations are ongoing There are still hostages being held inside Gaza. Journalists moving around freely could unknowingly expose special forces missions, rescue routes, or intelligence collection. 5. Hamas is a danger to journalists There is a real risk of kidnapping, hostage-taking, or worse. If anything happens, Israel would be blamed, even if it had no control. Hamas would use it for political leverage and media attention. 6. Military secrecy is critical Letting journalists film combat zones in real time would reveal IDF positions, tunnel clearing operations, or drone movements. That puts lives at risk and hands valuable intel to the enemy. 7. Legal and diplomatic fallout If a journalist is killed in Gaza, Israel is the one the world turns on. Lawsuits, outrage, and diplomatic pressure would follow immediately, even if Hamas was responsible. 8. The double standard is obvious No one allows free press access to Russian frontlines, Chinese military zones, or US drone strike areas. But Israel is constantly criticized for following the same basic security rules. So no, Piers. Letting journalists “decide for themselves” is not a solution. This is not a panel discussion. This is war. And in war, protecting lives comes first. It comes before press access, before media narratives, and definitely before letting journalists wander into combat zones just to “verify” what they already think they know. Why would Israel take the risk of journalists unintentionally (or intentionally) exposing troop positions or feeding Hamas coordinates? The reality is, the press as you and I know, has not proven itself a friend to Israel. And beyond that, the idea of reporters roaming freely through Gaza in the middle of battle is not journalism. It is insanity.
0:40

Piers Morgan keeps asking the same question in every interview: “Why is Israel intentionally killing civilians?” The answer is always the same. Israel is not targeting civilians. But Piers Morgan does not accept that. He cites the Hamas-run “Palestinian Ministry of Health” or “UK doctors operating in Gaza” as if British surgeons in a war zone can somehow tell whether a bullet came from Hamas or the IDF. When a guest says they do not trust Hamas’ numbers, Piers quickly shifts to his next question: “Then why won’t Israel let journalists into Gaza?” Here is the truth. Israel actually does allow journalists into Gaza, but not freely. They must coordinate, be escorted, and follow safety protocols. Piers then compares this to journalists visiting Israeli communities after October 7. That is a completely different situation. There were no ongoing combat operations, no terrorists hiding nearby, and no risk to Israeli troops or reporters. Then Piers says, “Let the journalists decide for themselves.” That might sound good on air, but it ignores reality. Here is why journalists cannot enter Gaza freely. The risks are real, and the cost far outweighs the benefit. 1. Gaza is an active combat zone No army on Earth allows reporters to wander freely in the middle of live military operations. The IDF is engaged in direct fighting with terror cells. Journalists could be killed or compromise critical missions. 2. Hamas controls everything There is no such thing as a free press in Gaza. Reporters are censored, monitored, and threatened. If they film rocket launches or armed fighters, they risk being detained or expelled. Most know this and self-censor. The result is pure propaganda. 3. Hamas hides behind civilians Terrorists wear civilian clothes and operate from civilian buildings. That makes it impossible for reporters to tell who is who, and it leads to heavily distorted reporting. 4. Hostage operations are ongoing There are still hostages being held inside Gaza. Journalists moving around freely could unknowingly expose special forces missions, rescue routes, or intelligence collection. 5. Hamas is a danger to journalists There is a real risk of kidnapping, hostage-taking, or worse. If anything happens, Israel would be blamed, even if it had no control. Hamas would use it for political leverage and media attention. 6. Military secrecy is critical Letting journalists film combat zones in real time would reveal IDF positions, tunnel clearing operations, or drone movements. That puts lives at risk and hands valuable intel to the enemy. 7. Legal and diplomatic fallout If a journalist is killed in Gaza, Israel is the one the world turns on. Lawsuits, outrage, and diplomatic pressure would follow immediately, even if Hamas was responsible. 8. The double standard is obvious No one allows free press access to Russian frontlines, Chinese military zones, or US drone strike areas. But Israel is constantly criticized for following the same basic security rules. So no, Piers. Letting journalists “decide for themselves” is not a solution. This is not a panel discussion. This is war. And in war, protecting lives comes first. It comes before press access, before media narratives, and definitely before letting journalists wander into combat zones just to “verify” what they already think they know. Why would Israel take the risk of journalists unintentionally (or intentionally) exposing troop positions or feeding Hamas coordinates? The reality is, the press as you and I know, has not proven itself a friend to Israel. And beyond that, the idea of reporters roaming freely through Gaza in the middle of battle is not journalism. It is insanity.

Open Source Intel

1,179,574 views • 1 year ago

Google just confirmed the first case of hackers using AI to build a zero-day exploit from scratch. An actual zero-day vulnerability that no human had EVER found before, discovered by an AI model, turned into a working weapon, and aimed at a mass exploitation campaign targeting thousands of systems simultaneously. Google's Threat Intelligence Group caught it yesterday and killed the operation before it scaled. But the details of how it worked are genuinely scary: The AI found a flaw in a popular two-factor authentication system that traditional security tools had missed entirely. The vulnerability was a logic error buried deep in the authentication flow where a developer had hard-coded a trust exception years ago. No human security researcher or automated scanner had caught it. The flaw was invisible to EVERY tool the cybersecurity industry has built over the past two decades. But the AI spotted it immediately. Then it wrote a full Python exploit script to weaponize it. Google's analysts could tell the code was AI-generated because it had textbook formatting, educational comments explaining every function, and even a hallucinated severity score that doesn't exist in any real database. The AI literally graded its own attack with a fake rating. So the code had MISTAKES in it. The criminals' implementation was clumsy enough that it probably interfered with the actual deployment. This was the sloppy first attempt by people who are still learning how to use these tools. And it still found a vulnerability that the entire cybersecurity industry missed. Google's chief threat analyst John Hultquist said: "There's a misconception that the AI vulnerability race is imminent. The reality is that it's already begun. For every zero-day we can trace back to AI, there are probably many more out there." But here's where it gets truly insane... This wasn't even a sophisticated operation. North Korea's APT45 hacking unit is sending thousands of repetitive prompts to AI models, recursively analyzing known vulnerabilities and building an entire exploit arsenal that would be physically impossible for human hackers to assemble at the same speed. They're essentially industrializing cyberattacks. A Chinese state-linked group jailbroke Google's own Gemini by simply asking it to "pretend to be a network security expert" and then used that persona to research how to hack TP-Link routers and corporate file transfer systems. Another Chinese group deployed autonomous AI agents that probed a Japanese tech firm with minimal human oversight, deciding on their own which tools to use and pivoting between targets based on internal reasoning. And then there's PROMPTSPY, an Android backdoor that calls Google's Gemini API to read your phone screen in real time, navigate your interface autonomously, capture your biometric data, replay your lock screen PIN, and block you from uninstalling it by placing an invisible overlay over the uninstall button. It literally OPERATES your phone using commercial AI tools anyone can access. Everyone spent the last 3 years arguing about whether AI would take people's jobs. Meanwhile AI is making every password, every firewall, and every two-factor authentication system on Earth fundamentally less secure. The entire $190 billion cybersecurity industry was built on one assumption: that finding vulnerabilities is hard and requires deep expertise. But AI just removed that assumption from the equation. And the scariest part is that Google said the criminals made errors this time. The implementation was rough and the campaign probably didn't fully work. These were amateurs, now imagine what professionals are able to do. There's a reason Sam Altman predicted an inevitable massive cyberattack THIS year. What do you think?
1:45

Google just confirmed the first case of hackers using AI to build a zero-day exploit from scratch. An actual zero-day vulnerability that no human had EVER found before, discovered by an AI model, turned into a working weapon, and aimed at a mass exploitation campaign targeting thousands of systems simultaneously. Google's Threat Intelligence Group caught it yesterday and killed the operation before it scaled. But the details of how it worked are genuinely scary: The AI found a flaw in a popular two-factor authentication system that traditional security tools had missed entirely. The vulnerability was a logic error buried deep in the authentication flow where a developer had hard-coded a trust exception years ago. No human security researcher or automated scanner had caught it. The flaw was invisible to EVERY tool the cybersecurity industry has built over the past two decades. But the AI spotted it immediately. Then it wrote a full Python exploit script to weaponize it. Google's analysts could tell the code was AI-generated because it had textbook formatting, educational comments explaining every function, and even a hallucinated severity score that doesn't exist in any real database. The AI literally graded its own attack with a fake rating. So the code had MISTAKES in it. The criminals' implementation was clumsy enough that it probably interfered with the actual deployment. This was the sloppy first attempt by people who are still learning how to use these tools. And it still found a vulnerability that the entire cybersecurity industry missed. Google's chief threat analyst John Hultquist said: "There's a misconception that the AI vulnerability race is imminent. The reality is that it's already begun. For every zero-day we can trace back to AI, there are probably many more out there." But here's where it gets truly insane... This wasn't even a sophisticated operation. North Korea's APT45 hacking unit is sending thousands of repetitive prompts to AI models, recursively analyzing known vulnerabilities and building an entire exploit arsenal that would be physically impossible for human hackers to assemble at the same speed. They're essentially industrializing cyberattacks. A Chinese state-linked group jailbroke Google's own Gemini by simply asking it to "pretend to be a network security expert" and then used that persona to research how to hack TP-Link routers and corporate file transfer systems. Another Chinese group deployed autonomous AI agents that probed a Japanese tech firm with minimal human oversight, deciding on their own which tools to use and pivoting between targets based on internal reasoning. And then there's PROMPTSPY, an Android backdoor that calls Google's Gemini API to read your phone screen in real time, navigate your interface autonomously, capture your biometric data, replay your lock screen PIN, and block you from uninstalling it by placing an invisible overlay over the uninstall button. It literally OPERATES your phone using commercial AI tools anyone can access. Everyone spent the last 3 years arguing about whether AI would take people's jobs. Meanwhile AI is making every password, every firewall, and every two-factor authentication system on Earth fundamentally less secure. The entire $190 billion cybersecurity industry was built on one assumption: that finding vulnerabilities is hard and requires deep expertise. But AI just removed that assumption from the equation. And the scariest part is that Google said the criminals made errors this time. The implementation was rough and the campaign probably didn't fully work. These were amateurs, now imagine what professionals are able to do. There's a reason Sam Altman predicted an inevitable massive cyberattack THIS year. What do you think?

Ricardo

50,564 views • 4 months ago

Dear ICP community, the Internet Computer has now been running strong for 5 years 👏👏👏 Here is a celebratory preview of ICP "cloud engines," the sovereign frontier cloud technology the network shall soon provide from Main points: — Cloud engines enable anyone to spin up their own sovereign frontier cloud. The technology involves an extraordinary inventive step, in which cloud is created from a mathematically secure network of nodes. The nodes run as part of the Internet Computer network ( but are selected and configured by the cloud engine's owner. — The frontier cloud provided by engines is strongly focused on enabling AI agents to build and update online applications and services for us. The world is changing fast, and nearly all new online apps and services are already being built with the help of AI, and thus cloud engines target the future of cloud. — Software hosted on cloud engines is tamperproof, which means that it is immune to infrastructure hacks, because it runs inside a mathematically secure network protocol, rather than on computers directly. This means that AI agents, and those building with them, don't need to have a security team in the loop, or to trust someone else's security team. This is crucial, because in the future, non technical people will demand the freedom to build with full automation — where they just need to issue instructions to AI about what to build, and don't need to worry about anything or anyone else. Of course, apps and services running on engines are also vastly safer from the new breed of hacker being enabled by frontier AI. (The cloud engines themselves are also "tamperproof." Even if a hacker gains physical access to some portion of a cloud engine's nodes, and can make arbitrary changes, the computations and data of the hosted apps and services cannot be corrupted or interrupted so long as the network's fault bounds aren't exceeded. The recent hack of Vercel, a major cloud platform, which gave hackers access to the apps it hosted, provides additional perspective on the importance of this advantage.) — Software hosted on cloud engines is guaranteed to run, so long as a sufficient number of the engine's nodes are running. This means that AI can build applications and services without the need to have a human systems admin team constantly tinkering with the underlying platform to keep it running, which is again crucial, because in the future, non technical people will expect the freedom to use AI to build without the support of others. — New frontier programming language technology, in the form of the Motoko language developed by Caffeine Labs, leverages seminal "orthogonal persistence" technology that unifies program logic and data to deliver further unlocks for AI (Motoko is the first computer language being developed that targets agents that are writing software rather than humans engineers per se). Nowadays, AI can build and update production apps at a prodigious rate, even at the speed of conversation. But it can also make mistakes, and there's a risk that an update it creates might be "lossy" in the sense it causes some transformed data to be lost. Again, in this new world, it's both undesirable and impractical for everyone to have to have a systems admin team on-hand to detect lossy updates and roll them back, but Motoko provides a solution: it can detect new software updates are lossy before they are applied, reducing potentially catastrophic errors by AI to harmless coding retries. — Software hosted on cloud engines is "serverless" but unlike traditional serverless software, directly it directly incorporates data through "orthogonal persistence." Another key purpose is simplify backend software logic and fuel the modeling power of AI by increasing abstraction (sorry for the technical language!!!). Put simply, this enables AI to produce more sophisticated backends, faster, and at dramatically lower costs, as measured by the number AI API tokens consumed during coding. (Tip for the technical: orthogonal persistence is a new paradigm where "the program is the database," and data lives inside program variables, which is possible because it's as if hosted software runs forever in persistent memory). — An expanding database of skills at shall make it possible to develop and directly deploy apps and services to your cloud engines directly from Claude Code, Perplexity, Codex and other AI platforms. Further, your account on can be connected, so that new apps and updates created through conversation automatically appear hosted from your cloud engine. In the future, R&D is going to be very seamless. You converse with AI, and your secure and unstoppable apps or services are created or updated. Cloud engines are designed to directly support this "self-writing cloud" future where we can work hands-free. — Tech sovereignty is becoming a huge issue worldwide, with governments and corporations seeking to create sovereign tech stacks owing to geopolitical tensions. Increasingly, people are realizing that tech provided by foreign nations can come with hidden backdoors and kills switches, from the base platform, right up through hosted apps and services. ICP technology is open source, and those building on ICP using AI own their own source code. When you have the source code, you can verify that there are no backdoors, and when you own the source code thanks to AI, you can update it at will, freeing you from vendor lock-in. But cloud engines take sovereignty much further... — You create a cloud engine by selecting the nodes that will be combined. You can choose the class of nodes used, and their number, but more importantly, you can choose who operates the nodes, and where they are located. Almost any configuration is possible, because the Internet Computer scales the security privileges afforded to hosted software within the network according to configuration (software hosted on cloud engines can directly interoperate with software on other engines and traditional subnets, but base restrictions are applied according to security rules). A cloud engine can be created within a region such as Europe, to comply with regs such as GDPR, or completely within a sovereign state like Switzerland or Pakistan. But cloud engines go further still... — Sovereignty is also about freedom from vendor lock-in. Cloud engines are essentially ICP (Internet Computer Protocol) network configurations, and this means the underlying compute nodes they combine can be swapped out without interrupting their hosted apps and services. This is a big deal. In addition, cloud engines now support nodes that are instances running on Big Tech's clouds, in addition to nodes that are dedicated specialized hardware, as per the Gen I and Gen II nodes that dominate the Internet Computer today. For example, it is possible to have an engine running across different AWS data centers, say, and then reconfigure the engine to run across a mixture of AWS, Google, Azure and Hetzner for even more resilience, without the users of hosted apps and services noticing a thing. That's true freedom. — Sovereign AI is becoming increasingly important too, and cloud engines allow special "AI nodes" to be added to them, so that hosted software can perform inference on hardware provisioned by the owner from a location the owner has selected. Even though the AI nodes are only accessible within the cloud engine, they can still benefit from the forthcoming Internet Intelligence Gateway (IG), which will make it possible to validate inference performed on key frontier open weights LLMs, even when the inference is performed on completely independent AI clouds. When the results of inference are received, this technology can verify that neither the prompt+context (input) nor the inference result (output) have been modified, and that the results were produced by the precise LLM expected. This ensures that AI clouds don't cheat by running inference on cheaper models than are being paid for, and bad actors aren't modifying the inputs or outputs to surreptitiously insert advertising into results, say, or change facts, or insert malware when code is being generated. What's super cool about this technology is the cost of the verification is scalable. A very valuable additional security can be achieved with only 1-2% of extra cost. — Scaling apps and services when they hit capacity limits is another thorny problem that cloud engines help the world address. Engines make scaling possible without rewriting or reconfiguring software. The query workload capacity of hosted software can be horizontally scaled simply by adding new nodes to an engine, and nodes can also be added in geographical proximity to demand. Meanwhile, update workload capacity can first be scaled-up by swapping an engine's nodes out for the next class up, and then when no larger class of node is available, horizontally scaled-out by "splitting" the engine into two, which doubles available capacity. (Technical tip: horizontally scaling update capacity by splitting engines requires multi-canister architectures). — For those who have been following how Caffeine builds apps that can efficiently store large numbers of files, I should mention that apps built on cloud engines will also support the new ICP Blob Storage cloud network (since cloud engines currently have up to about 3 TB of memory, which apps storing large amounts of files can easily exceed). We are also working on allowing blob storage nodes to be added to cloud engines, to enable sovereign mass blob storage within an engine, similarly to how AI nodes can be added currently. — Lastly, but certainly not least, I should mention that cloud engines are multi-blockchain capable, and ready for digital assets, thanks to the clever math at their core. For example, an e-commerce service built on a cloud engine can securely accept and custody stablecoin payments, or a multi-chain DEX could be hosted. Further, engines can support software autonomy (software orchestrated and controlled by other autonomous software, in a decentralized way) and can themselves be orchestrated by SNS technology, and thus run autonomously too. Today, though, the focus is on *mainstream* cloud. This year, the cloud industry will generate approximately one trillion dollars in revenue. That number is already huge, but is expected to grow to two trillion dollars by 2030. After years of continuous development, which have seen more than $500m spent on R&D, the Internet Computer network is now tacking directly toward this mainstream cloud market with cloud engine technology. In their first version, cloud engines are not meant to be a cloud panacea. For example, currently they are not ideal for working with big data. You should use something like DataBricks for that. Cloud engines are carefully targeted at enabling AI to produce traditional online applications and services, including SaaS, in a safer and more productive way, which represents a new market segment with tremendous potential. Of course, DFINITY will continue to work relentlessly to push forward ICP's capabilities, so expect further developments. It's worth mentioning that this cloud segment isn't just about creating new apps and services using AI, it's also about replacing legacy systems and apps built on super expensive SaaS services. Caffeine Labs is working to produce technology (Caffeine Snorkel) that can study an enterprise's legacy systems and app built on SaaS, create replacement systems and apps, and migrate the data, while supporting key stakeholders through the process over email and chat, with full automation. Thus the legacy systems and SaaS markets shall also be addressed by cloud engines. Zooming out, and reasoning in a more metaphysical way, we believe, as we always have, that there is room for a new kind of cloud created by mathematical networks, that provides seminal advances in the fields of security and resilience, as well as true sovereignty and freedom from lock-in. That this same technology, with the help of additional technologies like orthogonal persistence and Motoko, enables AI to build for us without the need for so much oversight, and to create more backend sophistication while consuming fewer AI API tokens, enables ICP to bring game-changing advances to the world. Cloud engines will work synergistically with the Intelligence Gateway, which will enable apps and services running on engines to seamlessly leverage AI, wherever that AI is running, while providing verifiability at extremely low cost for open weights frontier models. We believe that cloud engines represent an inflection point in the storied history of the Internet Computer project, and I'm very proud to be sharing the details with you on the network's fifth birthday 💪 I'll be back with more news soon!!
19:06

Dear ICP community, the Internet Computer has now been running strong for 5 years 👏👏👏 Here is a celebratory preview of ICP "cloud engines," the sovereign frontier cloud technology the network shall soon provide from Main points: — Cloud engines enable anyone to spin up their own sovereign frontier cloud. The technology involves an extraordinary inventive step, in which cloud is created from a mathematically secure network of nodes. The nodes run as part of the Internet Computer network ( but are selected and configured by the cloud engine's owner. — The frontier cloud provided by engines is strongly focused on enabling AI agents to build and update online applications and services for us. The world is changing fast, and nearly all new online apps and services are already being built with the help of AI, and thus cloud engines target the future of cloud. — Software hosted on cloud engines is tamperproof, which means that it is immune to infrastructure hacks, because it runs inside a mathematically secure network protocol, rather than on computers directly. This means that AI agents, and those building with them, don't need to have a security team in the loop, or to trust someone else's security team. This is crucial, because in the future, non technical people will demand the freedom to build with full automation — where they just need to issue instructions to AI about what to build, and don't need to worry about anything or anyone else. Of course, apps and services running on engines are also vastly safer from the new breed of hacker being enabled by frontier AI. (The cloud engines themselves are also "tamperproof." Even if a hacker gains physical access to some portion of a cloud engine's nodes, and can make arbitrary changes, the computations and data of the hosted apps and services cannot be corrupted or interrupted so long as the network's fault bounds aren't exceeded. The recent hack of Vercel, a major cloud platform, which gave hackers access to the apps it hosted, provides additional perspective on the importance of this advantage.) — Software hosted on cloud engines is guaranteed to run, so long as a sufficient number of the engine's nodes are running. This means that AI can build applications and services without the need to have a human systems admin team constantly tinkering with the underlying platform to keep it running, which is again crucial, because in the future, non technical people will expect the freedom to use AI to build without the support of others. — New frontier programming language technology, in the form of the Motoko language developed by Caffeine Labs, leverages seminal "orthogonal persistence" technology that unifies program logic and data to deliver further unlocks for AI (Motoko is the first computer language being developed that targets agents that are writing software rather than humans engineers per se). Nowadays, AI can build and update production apps at a prodigious rate, even at the speed of conversation. But it can also make mistakes, and there's a risk that an update it creates might be "lossy" in the sense it causes some transformed data to be lost. Again, in this new world, it's both undesirable and impractical for everyone to have to have a systems admin team on-hand to detect lossy updates and roll them back, but Motoko provides a solution: it can detect new software updates are lossy before they are applied, reducing potentially catastrophic errors by AI to harmless coding retries. — Software hosted on cloud engines is "serverless" but unlike traditional serverless software, directly it directly incorporates data through "orthogonal persistence." Another key purpose is simplify backend software logic and fuel the modeling power of AI by increasing abstraction (sorry for the technical language!!!). Put simply, this enables AI to produce more sophisticated backends, faster, and at dramatically lower costs, as measured by the number AI API tokens consumed during coding. (Tip for the technical: orthogonal persistence is a new paradigm where "the program is the database," and data lives inside program variables, which is possible because it's as if hosted software runs forever in persistent memory). — An expanding database of skills at shall make it possible to develop and directly deploy apps and services to your cloud engines directly from Claude Code, Perplexity, Codex and other AI platforms. Further, your account on can be connected, so that new apps and updates created through conversation automatically appear hosted from your cloud engine. In the future, R&D is going to be very seamless. You converse with AI, and your secure and unstoppable apps or services are created or updated. Cloud engines are designed to directly support this "self-writing cloud" future where we can work hands-free. — Tech sovereignty is becoming a huge issue worldwide, with governments and corporations seeking to create sovereign tech stacks owing to geopolitical tensions. Increasingly, people are realizing that tech provided by foreign nations can come with hidden backdoors and kills switches, from the base platform, right up through hosted apps and services. ICP technology is open source, and those building on ICP using AI own their own source code. When you have the source code, you can verify that there are no backdoors, and when you own the source code thanks to AI, you can update it at will, freeing you from vendor lock-in. But cloud engines take sovereignty much further... — You create a cloud engine by selecting the nodes that will be combined. You can choose the class of nodes used, and their number, but more importantly, you can choose who operates the nodes, and where they are located. Almost any configuration is possible, because the Internet Computer scales the security privileges afforded to hosted software within the network according to configuration (software hosted on cloud engines can directly interoperate with software on other engines and traditional subnets, but base restrictions are applied according to security rules). A cloud engine can be created within a region such as Europe, to comply with regs such as GDPR, or completely within a sovereign state like Switzerland or Pakistan. But cloud engines go further still... — Sovereignty is also about freedom from vendor lock-in. Cloud engines are essentially ICP (Internet Computer Protocol) network configurations, and this means the underlying compute nodes they combine can be swapped out without interrupting their hosted apps and services. This is a big deal. In addition, cloud engines now support nodes that are instances running on Big Tech's clouds, in addition to nodes that are dedicated specialized hardware, as per the Gen I and Gen II nodes that dominate the Internet Computer today. For example, it is possible to have an engine running across different AWS data centers, say, and then reconfigure the engine to run across a mixture of AWS, Google, Azure and Hetzner for even more resilience, without the users of hosted apps and services noticing a thing. That's true freedom. — Sovereign AI is becoming increasingly important too, and cloud engines allow special "AI nodes" to be added to them, so that hosted software can perform inference on hardware provisioned by the owner from a location the owner has selected. Even though the AI nodes are only accessible within the cloud engine, they can still benefit from the forthcoming Internet Intelligence Gateway (IG), which will make it possible to validate inference performed on key frontier open weights LLMs, even when the inference is performed on completely independent AI clouds. When the results of inference are received, this technology can verify that neither the prompt+context (input) nor the inference result (output) have been modified, and that the results were produced by the precise LLM expected. This ensures that AI clouds don't cheat by running inference on cheaper models than are being paid for, and bad actors aren't modifying the inputs or outputs to surreptitiously insert advertising into results, say, or change facts, or insert malware when code is being generated. What's super cool about this technology is the cost of the verification is scalable. A very valuable additional security can be achieved with only 1-2% of extra cost. — Scaling apps and services when they hit capacity limits is another thorny problem that cloud engines help the world address. Engines make scaling possible without rewriting or reconfiguring software. The query workload capacity of hosted software can be horizontally scaled simply by adding new nodes to an engine, and nodes can also be added in geographical proximity to demand. Meanwhile, update workload capacity can first be scaled-up by swapping an engine's nodes out for the next class up, and then when no larger class of node is available, horizontally scaled-out by "splitting" the engine into two, which doubles available capacity. (Technical tip: horizontally scaling update capacity by splitting engines requires multi-canister architectures). — For those who have been following how Caffeine builds apps that can efficiently store large numbers of files, I should mention that apps built on cloud engines will also support the new ICP Blob Storage cloud network (since cloud engines currently have up to about 3 TB of memory, which apps storing large amounts of files can easily exceed). We are also working on allowing blob storage nodes to be added to cloud engines, to enable sovereign mass blob storage within an engine, similarly to how AI nodes can be added currently. — Lastly, but certainly not least, I should mention that cloud engines are multi-blockchain capable, and ready for digital assets, thanks to the clever math at their core. For example, an e-commerce service built on a cloud engine can securely accept and custody stablecoin payments, or a multi-chain DEX could be hosted. Further, engines can support software autonomy (software orchestrated and controlled by other autonomous software, in a decentralized way) and can themselves be orchestrated by SNS technology, and thus run autonomously too. Today, though, the focus is on *mainstream* cloud. This year, the cloud industry will generate approximately one trillion dollars in revenue. That number is already huge, but is expected to grow to two trillion dollars by 2030. After years of continuous development, which have seen more than $500m spent on R&D, the Internet Computer network is now tacking directly toward this mainstream cloud market with cloud engine technology. In their first version, cloud engines are not meant to be a cloud panacea. For example, currently they are not ideal for working with big data. You should use something like DataBricks for that. Cloud engines are carefully targeted at enabling AI to produce traditional online applications and services, including SaaS, in a safer and more productive way, which represents a new market segment with tremendous potential. Of course, DFINITY will continue to work relentlessly to push forward ICP's capabilities, so expect further developments. It's worth mentioning that this cloud segment isn't just about creating new apps and services using AI, it's also about replacing legacy systems and apps built on super expensive SaaS services. Caffeine Labs is working to produce technology (Caffeine Snorkel) that can study an enterprise's legacy systems and app built on SaaS, create replacement systems and apps, and migrate the data, while supporting key stakeholders through the process over email and chat, with full automation. Thus the legacy systems and SaaS markets shall also be addressed by cloud engines. Zooming out, and reasoning in a more metaphysical way, we believe, as we always have, that there is room for a new kind of cloud created by mathematical networks, that provides seminal advances in the fields of security and resilience, as well as true sovereignty and freedom from lock-in. That this same technology, with the help of additional technologies like orthogonal persistence and Motoko, enables AI to build for us without the need for so much oversight, and to create more backend sophistication while consuming fewer AI API tokens, enables ICP to bring game-changing advances to the world. Cloud engines will work synergistically with the Intelligence Gateway, which will enable apps and services running on engines to seamlessly leverage AI, wherever that AI is running, while providing verifiability at extremely low cost for open weights frontier models. We believe that cloud engines represent an inflection point in the storied history of the Internet Computer project, and I'm very proud to be sharing the details with you on the network's fifth birthday 💪 I'll be back with more news soon!!

dom | icp

318,046 views • 4 months ago

🇬🇧 IS CIVIL WAR IN BRITAIN UNAVOIDABLE? Elon says it's inevitable. And for once, the man who shot a car into space and saved free speech by buying Twitter might not be wrong. Britain isn’t headed toward civil war because people are racist, or bigoted, or paranoid. It’s because they’ve been lied to - again, and again, and again - and now they’re done pretending everything’s fine. Here’s the setup: Illegal immigration is through the roof. Thousands arrive via small boats, with no documents, no vetting, no plans. They’re housed in hotels at taxpayer expense - nice ones, too - while Brits sleep in cars, sofa-surf, or languish on council waitlists that stretch into eternity. And if you dare question any of it, the entire establishment pounces: how dare you? But the truth’s leaking out like a dinghy with a hole. People are being assaulted. Not by all migrants - of course not - but when you bring in tens of thousands without knowing who they are, some will be predators. And that risk, however small per capita, explodes in the aggregate. But pointing that out? Instant cancellation. Or worse - now they’re talking criminal charges under the Online Safety Act for “hate speech.” Translation: disagree with the narrative and we’ll shut you up. People are being told it’s their moral duty to foot the bill, shut their mouths, and smile while the country unravels. And to make that compliance seamless, here comes the next brilliant idea: digital ID. Yes, nothing says freedom like having your identity, online speech, and financial access tethered to a government app. You know, for “security.” Just like every authoritarian regime in history said before things got really fun. Brits aren’t stupid. They see the social contract being rewritten in real time. “We import chaos, you pay for it. We erase your speech, you clap. We lose control, you take the blame.” It’s 1984, except this time Winston Smith doesn’t even get the dignity of a telescreen - just a suspended social media account and a digital ID linked to his energy bill. And the government? They wag their fingers at “right-wing extremists” while spending billions to warehouse strangers from who-knows-where with no plan to send them back. Deportations are a joke. The backlog of asylum claims is a national embarrassment. But don’t worry, someone’s just launched another taskforce. Maybe they’ll have matching lanyards. People have had enough. Not of immigrants, per se - but of being gaslit by a political class that thinks they’re too stupid or too scared to notice the obvious. And when you push a population to the edge - tell them to shut up, fork over, and enjoy the ride - eventually, they push back. Hard. Is civil war inevitable? Hopefully not. But civic trust is cratering, speech is being criminalized, identity is being digitized, and reality is being denied. At some point, the British public stops asking politely and starts asking furiously. And when that day comes, no amount of “fact-checking” or PR spin will stop the blowback. The elites lit the fuse. The people are just waiting to see how long it burns.
0:45

🇬🇧 IS CIVIL WAR IN BRITAIN UNAVOIDABLE? Elon says it's inevitable. And for once, the man who shot a car into space and saved free speech by buying Twitter might not be wrong. Britain isn’t headed toward civil war because people are racist, or bigoted, or paranoid. It’s because they’ve been lied to - again, and again, and again - and now they’re done pretending everything’s fine. Here’s the setup: Illegal immigration is through the roof. Thousands arrive via small boats, with no documents, no vetting, no plans. They’re housed in hotels at taxpayer expense - nice ones, too - while Brits sleep in cars, sofa-surf, or languish on council waitlists that stretch into eternity. And if you dare question any of it, the entire establishment pounces: how dare you? But the truth’s leaking out like a dinghy with a hole. People are being assaulted. Not by all migrants - of course not - but when you bring in tens of thousands without knowing who they are, some will be predators. And that risk, however small per capita, explodes in the aggregate. But pointing that out? Instant cancellation. Or worse - now they’re talking criminal charges under the Online Safety Act for “hate speech.” Translation: disagree with the narrative and we’ll shut you up. People are being told it’s their moral duty to foot the bill, shut their mouths, and smile while the country unravels. And to make that compliance seamless, here comes the next brilliant idea: digital ID. Yes, nothing says freedom like having your identity, online speech, and financial access tethered to a government app. You know, for “security.” Just like every authoritarian regime in history said before things got really fun. Brits aren’t stupid. They see the social contract being rewritten in real time. “We import chaos, you pay for it. We erase your speech, you clap. We lose control, you take the blame.” It’s 1984, except this time Winston Smith doesn’t even get the dignity of a telescreen - just a suspended social media account and a digital ID linked to his energy bill. And the government? They wag their fingers at “right-wing extremists” while spending billions to warehouse strangers from who-knows-where with no plan to send them back. Deportations are a joke. The backlog of asylum claims is a national embarrassment. But don’t worry, someone’s just launched another taskforce. Maybe they’ll have matching lanyards. People have had enough. Not of immigrants, per se - but of being gaslit by a political class that thinks they’re too stupid or too scared to notice the obvious. And when you push a population to the edge - tell them to shut up, fork over, and enjoy the ride - eventually, they push back. Hard. Is civil war inevitable? Hopefully not. But civic trust is cratering, speech is being criminalized, identity is being digitized, and reality is being denied. At some point, the British public stops asking politely and starts asking furiously. And when that day comes, no amount of “fact-checking” or PR spin will stop the blowback. The elites lit the fuse. The people are just waiting to see how long it burns.

Mario Nawfal

2,886,729 views • 10 months ago

Hyperspace: The Agentic OS Apple Should Have Built On December 19th, 2024, we announced the world’s first Agentic Browser. What followed was a movement — a new category was born which led to many early products in this space and recently the hundreds of people lining up outside the The Agentic Browser Summit in San Francisco underscored that. Silicon Valley instinctively gets it, from students to tech executives, people can feel a revolutionary new change in computing is in the air. Past year taught us why such a product was inevitable, a hard engineering effort, and also the last mover in the entire software world this decade if and when done right. All paths are headed in the same direction: one tool which orchestrates them all. At Hyperspace we showed that path with essays and products we launched in earlier months: from a spatial UI of orchestrating agents, to showcasing transparent activity in how the AI system operates which leads to user trust, to presenting the software end-game, which massively improves human productivity. We also built the world’s largest AI network, drawing participation from people in almost 6000 cities around the world contributing their machines as nodes in the network. Think Uber, but for AI. That is, planetary-scale. And now we are stretching this industry ambition further with our end-to-end vision of the Agentic Supercomputer, the first breakthrough new AI OS, and an effort which spans from AI research to distributed systems to inventing a new UI to inventing a new business model to complement it. All of this together helps us in serving our mission, of delivering “Everyone’s Personal Supercomputer”. While others have built AI-native browsers, no one though has built something agentic from the ground up — with AI as the foundation, not a feature. How do you fundamentally improve the lives’ of billions around the world ? We believe that requires building a native environment for agents to be viewed, created, deployed, executed, discovered and priced in. That is a world where we move on from static apps, to dynamic agents. But, as my 2 year old niece likes to ask: “but why ?” The issue is that the world of software today is fragmented, and everyone is sprinkling on AI as a feature and charging a subscription fees for it. From browser makers, to IDEs, to design and other productivity tools. This leads to a fragmented UX, where people have to learn to use AI in each app, their memory and other context is not shared between all these apps, and they also have to pay separately for compute for each such AI-enhanced app. Each app maker has to figure out basics such as compute, and leads to the issues we saw with Cursor pricing recently. This is not the future. What if AI was the foundation instead of a feature ? What if Apple had built a fundamentally new AI OS from the ground up and what would it have looked like ? At Hyperspace, that is what we did. On July 15th we introduced three breakthrough key pillars of our AI OS: 1. Agentic Browser 2. Agentic Memory 3. Agentic Payments And we didn’t stop there. We also introduced a breakthrough new user interface called the Spatial AI which is inspired both from the spreadsheet and the HyperCard - each card is an agent, with it’s own inputs and outputs, endlessly extensible and pluggable with others, just like cells of a spreadsheet. Update one cell and all the dependents update, like a spreadsheet formula. It goes beyond a static linear workflow to being able to operate in all directions. This revolutionary new interface helps manage all of the below: 1. Multiple websites being browsed in parallel 2. Multiple desktop apps being browsed in parallel 3. Multiple server tools being used in parallel 4. Multiple smartphone apps streamed to your device or opened via an emulator All the software which you need comes together in this one seamless, agent-native interface. This interface provides you access to the largest network of models, vectors, agents and compute on the planet. The Browser. The IDE. The Notepad… they are not separate products: they are all in one, the Agentic Browser. As Steve Jobs famously said at the iPhone announcement, “are you getting it ?” And beneath this UI lies a new intelligence routing layer — leveraging both swarms of specialized models to the Hyperspace Matrix model that recalls thousands of tools in real-time, not by context window hacks, but through retrieval, ranking, and reuse. To many, this will feel like AGI. Not one big system by one big company, but an intelligent network. Now lets talk about privacy… Are you comfortable with one company owning all your memory forever ? I am not. So we have invented Agentic Memory as a new open protocol which provides full power over memory to you, the user. Your memory is yours, encrypted, on your device, and portable if and how you want. Anyone can build on it without our permission, but not without your permission. This protocol, and the decentralized vector database spread out across the world, would enable apps and agents to share context and memory. Think copy-paste, but for the AI world. It doesn’t just remember — it knows what matters. VectorRank helps your AI weigh your life’s most relevant moments over time, just like the way our minds elevate memories. Now each time you use an agent, your experience with other agents will also continuously improve: you don’t have to keep repeating the same things about yourself, while fully preserving your privacy. Agentic Memory is accessible within the Agentic Browser to manage. And there is one more thing… AI as the foundation requires compute to be available at the base layer, but this base layer spans models running on your own device, to cloud APIs, to also running across the peer-to-peer distributed network. Agentic Payments provides a singular interface to all of that compute, running a spot auction clearing marketplace every second to determine the fair price of compute. This results in price transparency, and you as the user paying the lowest possible cost. If you want predictability, you can reserve compute in advance. This end-to-end system provides the most streamlined world for agents to operate in. In order to enable this world and the world of agents being able to pay each other in sub-cent increments millions of times a second, we had to also invent a fundamentally new agentic micropayments blockchain. All of this together would enable a world where you as a user, or the agent itself, can efficiently call and utilize other agents built by others and also pay for content which is unique and useful. This enables a move away from the current AI exploitative economy for bloggers and other content creators, to a web with a fundamental new business model. Earlier we didn’t have the right infrastructure to enable such a world. Now, all the dots connect. The Hyperspace AI OS would give the power of a supercomputer in everyone’s hands. This isn’t a browser, or an IDE or limited to any device or cloud. It’s an entire AI operating system — with a breakthrough new spatial UI, local and distributed compute, agentic memory, agentic payments, and orchestration built into the foundation. As a user, we move the choice back in your hands with an experience you will love and find delightful. You get to choose the level of privacy, cost, and utility you want. And while Apple should have done it, we could not wait, and we feel this just required a new level of passion and DNA which we bring here. We are just getting started. Thank you, Varun Mathur Cofounder and CEO, Hyperspace cc Naval Marc Andreessen 🇺🇸 Vinod Khosla Andrej Karpathy Sam Altman
2:52

Hyperspace: The Agentic OS Apple Should Have Built On December 19th, 2024, we announced the world’s first Agentic Browser. What followed was a movement — a new category was born which led to many early products in this space and recently the hundreds of people lining up outside the The Agentic Browser Summit in San Francisco underscored that. Silicon Valley instinctively gets it, from students to tech executives, people can feel a revolutionary new change in computing is in the air. Past year taught us why such a product was inevitable, a hard engineering effort, and also the last mover in the entire software world this decade if and when done right. All paths are headed in the same direction: one tool which orchestrates them all. At Hyperspace we showed that path with essays and products we launched in earlier months: from a spatial UI of orchestrating agents, to showcasing transparent activity in how the AI system operates which leads to user trust, to presenting the software end-game, which massively improves human productivity. We also built the world’s largest AI network, drawing participation from people in almost 6000 cities around the world contributing their machines as nodes in the network. Think Uber, but for AI. That is, planetary-scale. And now we are stretching this industry ambition further with our end-to-end vision of the Agentic Supercomputer, the first breakthrough new AI OS, and an effort which spans from AI research to distributed systems to inventing a new UI to inventing a new business model to complement it. All of this together helps us in serving our mission, of delivering “Everyone’s Personal Supercomputer”. While others have built AI-native browsers, no one though has built something agentic from the ground up — with AI as the foundation, not a feature. How do you fundamentally improve the lives’ of billions around the world ? We believe that requires building a native environment for agents to be viewed, created, deployed, executed, discovered and priced in. That is a world where we move on from static apps, to dynamic agents. But, as my 2 year old niece likes to ask: “but why ?” The issue is that the world of software today is fragmented, and everyone is sprinkling on AI as a feature and charging a subscription fees for it. From browser makers, to IDEs, to design and other productivity tools. This leads to a fragmented UX, where people have to learn to use AI in each app, their memory and other context is not shared between all these apps, and they also have to pay separately for compute for each such AI-enhanced app. Each app maker has to figure out basics such as compute, and leads to the issues we saw with Cursor pricing recently. This is not the future. What if AI was the foundation instead of a feature ? What if Apple had built a fundamentally new AI OS from the ground up and what would it have looked like ? At Hyperspace, that is what we did. On July 15th we introduced three breakthrough key pillars of our AI OS: 1. Agentic Browser 2. Agentic Memory 3. Agentic Payments And we didn’t stop there. We also introduced a breakthrough new user interface called the Spatial AI which is inspired both from the spreadsheet and the HyperCard - each card is an agent, with it’s own inputs and outputs, endlessly extensible and pluggable with others, just like cells of a spreadsheet. Update one cell and all the dependents update, like a spreadsheet formula. It goes beyond a static linear workflow to being able to operate in all directions. This revolutionary new interface helps manage all of the below: 1. Multiple websites being browsed in parallel 2. Multiple desktop apps being browsed in parallel 3. Multiple server tools being used in parallel 4. Multiple smartphone apps streamed to your device or opened via an emulator All the software which you need comes together in this one seamless, agent-native interface. This interface provides you access to the largest network of models, vectors, agents and compute on the planet. The Browser. The IDE. The Notepad… they are not separate products: they are all in one, the Agentic Browser. As Steve Jobs famously said at the iPhone announcement, “are you getting it ?” And beneath this UI lies a new intelligence routing layer — leveraging both swarms of specialized models to the Hyperspace Matrix model that recalls thousands of tools in real-time, not by context window hacks, but through retrieval, ranking, and reuse. To many, this will feel like AGI. Not one big system by one big company, but an intelligent network. Now lets talk about privacy… Are you comfortable with one company owning all your memory forever ? I am not. So we have invented Agentic Memory as a new open protocol which provides full power over memory to you, the user. Your memory is yours, encrypted, on your device, and portable if and how you want. Anyone can build on it without our permission, but not without your permission. This protocol, and the decentralized vector database spread out across the world, would enable apps and agents to share context and memory. Think copy-paste, but for the AI world. It doesn’t just remember — it knows what matters. VectorRank helps your AI weigh your life’s most relevant moments over time, just like the way our minds elevate memories. Now each time you use an agent, your experience with other agents will also continuously improve: you don’t have to keep repeating the same things about yourself, while fully preserving your privacy. Agentic Memory is accessible within the Agentic Browser to manage. And there is one more thing… AI as the foundation requires compute to be available at the base layer, but this base layer spans models running on your own device, to cloud APIs, to also running across the peer-to-peer distributed network. Agentic Payments provides a singular interface to all of that compute, running a spot auction clearing marketplace every second to determine the fair price of compute. This results in price transparency, and you as the user paying the lowest possible cost. If you want predictability, you can reserve compute in advance. This end-to-end system provides the most streamlined world for agents to operate in. In order to enable this world and the world of agents being able to pay each other in sub-cent increments millions of times a second, we had to also invent a fundamentally new agentic micropayments blockchain. All of this together would enable a world where you as a user, or the agent itself, can efficiently call and utilize other agents built by others and also pay for content which is unique and useful. This enables a move away from the current AI exploitative economy for bloggers and other content creators, to a web with a fundamental new business model. Earlier we didn’t have the right infrastructure to enable such a world. Now, all the dots connect. The Hyperspace AI OS would give the power of a supercomputer in everyone’s hands. This isn’t a browser, or an IDE or limited to any device or cloud. It’s an entire AI operating system — with a breakthrough new spatial UI, local and distributed compute, agentic memory, agentic payments, and orchestration built into the foundation. As a user, we move the choice back in your hands with an experience you will love and find delightful. You get to choose the level of privacy, cost, and utility you want. And while Apple should have done it, we could not wait, and we feel this just required a new level of passion and DNA which we bring here. We are just getting started. Thank you, Varun Mathur Cofounder and CEO, Hyperspace cc Naval Marc Andreessen 🇺🇸 Vinod Khosla Andrej Karpathy Sam Altman

Varun

169,177 views • 1 year ago

Carney's Public Safety Minister has ties to terror groups — he needs to be fired! Would you trust your family’s safety to a guy who’s literally banned from dealing with terrorist threats — because of his own connections to them? No? Well, too bad. Because that guy’s name is Gary Anandasangaree, and he’s your federal Public Safety Minister. Canada’s Public Safety Minister is too compromised to handle public safety. That’s not a punchline — it’s the actual state of affairs in Carney's Liberal circus. Gary Anandasangaree, the guy tasked with keeping you safe from domestic foreign threats, can’t even be briefed on files related to a known terrorist organization, the Tamil Tigers — because he’s been personally involved with their Canadian front groups. But instead of stepping down, Anandasangaree has simply recused himself from dealing with them. Let’s walk through this slowly so even CBC journalists can follow along. In 2014, the Sri Lankan government — not some alt-right blog — warned Canada that Anandasangaree had deep ties to the Tamil Tigers. The Liberation Tigers of Tamil Eelam. A banned terrorist organization in Canada. You’d think that might give a government some pause before handing this guy the national security portfolio. But nope. Carney made him Public Safety Minister. You know, the guy who’s supposed to oversee CSIS, the RCMP, terror listings, the works. And then what happens? We find out from Global News that Anandasangaree personally vouched for a man linked to the Tamil Tigers in his immigration appeal. This wasn’t a distant acquaintance. He wrote two letters of support saying Canada should let the guy in — a man CBSA said was part of a known terror group, involved in propaganda, intimidation and fundraising. He said that decision to bar the guy was ‘an error.’ You know what’s an error? Putting a man with deep political ties to a banned militant group in charge of national security. Anandasangaree has quietly removed himself from any files involving the Tamil Tigers or their Canadian arm, the World Tamil Movement. Which raises the obvious question: who is overseeing those files now? Who’s protecting Canadians from threats that Anandasangaree is too compromised to touch? Nobody seems to know. And Carney isn’t saying. You can’t be in charge of Public Safety if you have to put asterisk after ‘public’ and ‘safety.’ This isn’t just poor judgment. It’s a national security risk. This is the kind of conflict of interest that gets people in other countries removed from office. Here in Canada, it gets you a cabinet post and a raise. If this government cared even a little about safety, transparency, or basic decency, Anandasangaree would be gone already. But they don’t. They care about identity politics, fundraising from the Tamil diaspora, and loyalty to the party — full stop. So, it’s up to us. Carney won’t do the right thing. Anandasangaree isn't known for his good judgment. That’s why we made a website. REPORT by Sheila Gunn Reid:
4:32

Carney's Public Safety Minister has ties to terror groups — he needs to be fired! Would you trust your family’s safety to a guy who’s literally banned from dealing with terrorist threats — because of his own connections to them? No? Well, too bad. Because that guy’s name is Gary Anandasangaree, and he’s your federal Public Safety Minister. Canada’s Public Safety Minister is too compromised to handle public safety. That’s not a punchline — it’s the actual state of affairs in Carney's Liberal circus. Gary Anandasangaree, the guy tasked with keeping you safe from domestic foreign threats, can’t even be briefed on files related to a known terrorist organization, the Tamil Tigers — because he’s been personally involved with their Canadian front groups. But instead of stepping down, Anandasangaree has simply recused himself from dealing with them. Let’s walk through this slowly so even CBC journalists can follow along. In 2014, the Sri Lankan government — not some alt-right blog — warned Canada that Anandasangaree had deep ties to the Tamil Tigers. The Liberation Tigers of Tamil Eelam. A banned terrorist organization in Canada. You’d think that might give a government some pause before handing this guy the national security portfolio. But nope. Carney made him Public Safety Minister. You know, the guy who’s supposed to oversee CSIS, the RCMP, terror listings, the works. And then what happens? We find out from Global News that Anandasangaree personally vouched for a man linked to the Tamil Tigers in his immigration appeal. This wasn’t a distant acquaintance. He wrote two letters of support saying Canada should let the guy in — a man CBSA said was part of a known terror group, involved in propaganda, intimidation and fundraising. He said that decision to bar the guy was ‘an error.’ You know what’s an error? Putting a man with deep political ties to a banned militant group in charge of national security. Anandasangaree has quietly removed himself from any files involving the Tamil Tigers or their Canadian arm, the World Tamil Movement. Which raises the obvious question: who is overseeing those files now? Who’s protecting Canadians from threats that Anandasangaree is too compromised to touch? Nobody seems to know. And Carney isn’t saying. You can’t be in charge of Public Safety if you have to put asterisk after ‘public’ and ‘safety.’ This isn’t just poor judgment. It’s a national security risk. This is the kind of conflict of interest that gets people in other countries removed from office. Here in Canada, it gets you a cabinet post and a raise. If this government cared even a little about safety, transparency, or basic decency, Anandasangaree would be gone already. But they don’t. They care about identity politics, fundraising from the Tamil diaspora, and loyalty to the party — full stop. So, it’s up to us. Carney won’t do the right thing. Anandasangaree isn't known for his good judgment. That’s why we made a website. REPORT by Sheila Gunn Reid:

Rebel News

15,890 views • 1 year ago