Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

I recently explored TinyFish, a web agents API. What stood out wasn’t hype. It treats the web like infrastructure. Natural language goal in → multi-site execution → structured data out. Less “AI magic.” More systems thinking.

49,720 görüntüleme • 5 ay önce •via X (Twitter)

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

In 2025, the AgentFlayer exploit highlighted a new category of risk in AI systems. It was not a traditional breach involving stolen credentials or broken encryption. Instead, it demonstrated how an autonomous AI agent could be manipulated into executing unintended actions by processing malicious instructions embedded inside content it automatically processes. The incident did not expose a flaw in one specific integration. It revealed a structural weakness in how many modern AI agents are built. Today’s agents are no longer passive language models. They read documents automatically, scan emails, connect to SaaS tools, access cloud storage, and execute actions across multiple systems. To be useful, they are granted meaningful permissions. That capability creates value, but it also expands the attack surface. Most agent environments operate in a trusted, plaintext execution model. Data is encrypted at rest and in transit, but it is typically decrypted during inference so the model can process it. That runtime visibility is where potential risk lies. In a zero-click scenario like AgentFlayer, an attacker can embed hidden instructions inside a document that the AI processes automatically. Because the agent may have access to connected systems such as Google Drive, Slack, or GitHub, it can potentially be influenced to retrieve sensitive information or perform unintended actions. The user does not need to click a malicious link or approve a suspicious request. Therefore, the core issue is that during execution, the system may have access to sensitive data and broad privileges, meaning whoever controls the execution environment ultimately controls access to that data. Now consider a different architectural approach. If a system is designed so that data remains protected during execution, the risk profile changes. On Nesa, privacy is enforced at the execution layer through Equivariant Encryption. Computation can occur on encrypted data, reducing the visibility surface during runtime. Sensitive inputs and models do not need to be exposed in plain text to infrastructure operators for inference to occur. This does not eliminate prompt injection, logic manipulation, or tool misuse. Encryption alone cannot prevent an agent from being instructed to take an unintended action if it has been granted that permission. What it does do is materially reduce confidentiality risk. By limiting access to readable sensitive data during execution and reducing unilateral visibility at the infrastructure layer, the potential blast radius of a successful manipulation attempt is constrained. As AI agents become more autonomous and embedded into enterprise workflows, security must move deeper into architecture. The goal is not to claim invulnerability. It is to reduce trust concentration and contain systemic exposure when failures occur. AgentFlayer was not simply a one-off exploit. It was a reminder that in autonomous systems, execution-layer design determines how risk propagates.

Nesa

17,038 görüntüleme • 5 ay önce

I just built a complete SEO audit plugin in Claude Code that replaces your $200/mo Ahrefs subscription 🤯 One Claude Plugin audits any store: technical SEO, product schema, content, Core Web Vitals, and AI-search readiness. Parallel agents, a 0-100 score, and a dashboard that renders right in the panel. All inside Claude Code. So I pointed it at Ridge .com, one of the sharpest DTC operators out there. It came back 56/100, and what stood out wasn't a knock on them at all: Ridge has a better AI-commerce setup than 99% of stores. A real llms.txt, an agent-discovery sitemap, a live MCP endpoint, genuinely ahead of the curve. And even on a store that dialed-in, the audit surfaced fixable gaps in ~90 seconds: → Room to add product structured data → A mobile Core Web Vitals score worth tightening → A thin meta description on a high-traffic collection Perfect for e-comm operators and SEO agencies who are sick of paying $200/mo for tools that bury the real issues, running quarterly audits that take a week, and shipping reports nobody can act on. So I put together the full playbook to build your own. The complete guide to building this Plugin in Claude Code: branded to you, tuned to exactly how you audit, repeatable across every client. The kind of audit you run in minutes and hand over as a deliverable that looks like it cost thousands. What's inside: → The architecture (orchestrator + parallel sub-agents) → How to fetch any store past Cloudflare → The 0-100 scoring + falsifiable-findings framework → How to ship the HTML dashboard for client demos → The full build, start to finish Want the playbook for free? > Like this post > Comment "SEO" And I'll send it over (must be following so I can DM)

Mike Futia

55,431 görüntüleme • 2 ay önce