<?xml version="1.0" encoding="UTF-8"?><feed xmlns="http://www.w3.org/2005/Atom"><title>Web3Sec working library</title><id>https://www.web3sec.news/blog</id><link href="https://www.web3sec.news/feed.xml" rel="self"/><link href="https://www.web3sec.news/blog"/><updated>2026-11-08T00:00:00Z</updated><author><name>Raiders / Web3Sec</name></author><entry><id>https://www.web3sec.news/blog/nomad-initialization-trust</id><title>Nomad: when an initialized default becomes permission to process a message</title><link href="https://www.web3sec.news/blog/nomad-initialization-trust"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>A bridge authentication failure illustrates why deployment state, default values and upgrade behavior need a single security model.</summary></entry><entry><id>https://www.web3sec.news/blog/euler-donation-accounting</id><title>Euler V1: every path that changes collateral belongs in the solvency model</title><link href="https://www.web3sec.news/blog/euler-donation-accounting"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>The March 2023 exploit connects an omitted account-health check to liquidation incentives and multi-step accounting invariants.</summary></entry><entry><id>https://www.web3sec.news/blog/ledger-connect-kit-publishing</id><title>Ledger Connect Kit: offboarding and runtime dependencies share a security boundary</title><link href="https://www.web3sec.news/blog/ledger-connect-kit-publishing"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>A package-publishing compromise reached applications through dynamically loaded code without changing their own repositories.</summary></entry><entry><id>https://www.web3sec.news/blog/lastpass-vault-backups</id><title>LastPass 2022: backup access can be the production-data incident</title><link href="https://www.web3sec.news/blog/lastpass-vault-backups"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>The disclosed chain from development information to privileged endpoint compromise and stolen backups challenges narrow production boundaries.</summary></entry><entry><id>https://www.web3sec.news/blog/okta-support-session-tokens</id><title>Okta support system 2023: diagnostic files can carry live account authority</title><link href="https://www.web3sec.news/blog/okta-support-session-tokens"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>A support-system compromise links browser synchronization, service-account access and sensitive HAR files to session hijacking.</summary></entry><entry><id>https://www.web3sec.news/blog/nextjs-october-november-2026-security-advisories</id><title>Next.js October and November 2026 advisories: patch the deployed artifact</title><link href="https://www.web3sec.news/blog/nextjs-october-november-2026-security-advisories"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>Recent framework advisories connect upstream libraries, image processing, caching and cookie handling to the software actually running in production.</summary></entry><entry><id>https://www.web3sec.news/blog/bybit-safe-signing-boundary</id><title>Bybit and Safe: the signing interface is part of your security boundary</title><link href="https://www.web3sec.news/blog/bybit-safe-signing-boundary"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>The February 2025 theft shows why multiple signatures cannot compensate for a shared, compromised view of a transaction.</summary></entry><entry><id>https://www.web3sec.news/blog/radiant-capital-developer-opsec</id><title>Radiant Capital: a document request can become a treasury incident</title><link href="https://www.web3sec.news/blog/radiant-capital-developer-opsec"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>A reported malware delivery chain connects developer communications, workstation trust and multisig operations.</summary></entry><entry><id>https://www.web3sec.news/blog/wazirx-custody-responsibility</id><title>WazirX: make custody responsibilities testable before an incident</title><link href="https://www.web3sec.news/blog/wazirx-custody-responsibility"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>The July 2024 wallet theft illustrates the operational consequences of unclear verification and response responsibilities.</summary></entry><entry><id>https://www.web3sec.news/blog/snowflake-stolen-credentials</id><title>Snowflake customer intrusions: old credentials can remain a live attack path</title><link href="https://www.web3sec.news/blog/snowflake-stolen-credentials"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>Mandiant’s 2024 investigation connects infostealer exposure, missing MFA and cloud data theft.</summary></entry><entry><id>https://www.web3sec.news/blog/cloudflare-token-rotation</id><title>Cloudflare’s Thanksgiving incident: a rotation checklist needs closure evidence</title><link href="https://www.web3sec.news/blog/cloudflare-token-rotation"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>A 2024 disclosure about a 2023 intrusion shows how residual credentials can outlive an initial response.</summary></entry><entry><id>https://www.web3sec.news/blog/tj-actions-ci-secret-exposure</id><title>tj-actions compromise: CI logs can become a secret-exfiltration channel</title><link href="https://www.web3sec.news/blog/tj-actions-ci-secret-exposure"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>CVE-2025-30066 demonstrates why action versions, workflow permissions and build logs belong in one threat model.</summary></entry><entry><id>https://www.web3sec.news/blog/xz-build-artifact-trust</id><title>XZ backdoor: review the artifact you deploy, not only the repository</title><link href="https://www.web3sec.news/blog/xz-build-artifact-trust"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>CVE-2024-3094 illustrates the gap between source review, release packaging and the executable shipped downstream.</summary></entry><entry><id>https://www.web3sec.news/blog/ai-agents-prompt-injection-boundaries</id><title>AI agents: keep untrusted content away from authorization decisions</title><link href="https://www.web3sec.news/blog/ai-agents-prompt-injection-boundaries"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>A practical control model for assistants that read the web, inspect repositories and act through connected tools.</summary></entry><entry><id>https://www.web3sec.news/blog/identity-mfa-recovery-runbook</id><title>Identity security: phishing-resistant login, usable recovery and verified offboarding</title><link href="https://www.web3sec.news/blog/identity-mfa-recovery-runbook"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>An operating procedure for the accounts that control email, cloud infrastructure, source code and company recovery.</summary></entry><entry><id>https://www.web3sec.news/blog/email-account-security-runbook</id><title>Email security: protect the recovery inbox and control who can send as your domain</title><link href="https://www.web3sec.news/blog/email-account-security-runbook"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>Separate mailbox compromise, domain spoofing and support impersonation into controls with observable tests.</summary></entry><entry><id>https://www.web3sec.news/blog/domain-dns-security-runbook</id><title>Domain and DNS security: preserve control of the address your users trust</title><link href="https://www.web3sec.news/blog/domain-dns-security-runbook"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>A runbook for registrar ownership, scoped DNS changes, renewal resilience and safe nameserver recovery.</summary></entry><entry><id>https://www.web3sec.news/blog/developer-device-security-runbook</id><title>Developer device security: isolate experiments from production authority</title><link href="https://www.web3sec.news/blog/developer-device-security-runbook"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>A practical baseline for laptops that handle source code, external repositories, credentials and sensitive client material.</summary></entry><entry><id>https://www.web3sec.news/blog/browser-extension-security-runbook</id><title>Browser and extension security: reduce the code surrounding every privileged session</title><link href="https://www.web3sec.news/blog/browser-extension-security-runbook"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>Inventory permissions, separate sensitive browsing and prepare for malicious extensions or stolen browser sessions.</summary></entry><entry><id>https://www.web3sec.news/blog/github-ci-security-runbook</id><title>GitHub and CI/CD security: keep untrusted changes away from deployment authority</title><link href="https://www.web3sec.news/blog/github-ci-security-runbook"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>A review procedure for workflow triggers, action revisions, runner isolation and cloud deployment identity.</summary></entry><entry><id>https://www.web3sec.news/blog/package-publishing-security-runbook</id><title>Package publishing security: control who can ship and what consumers execute</title><link href="https://www.web3sec.news/blog/package-publishing-security-runbook"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>A practical process for registry access, trusted publishing, provenance, dependency review and compromised releases.</summary></entry><entry><id>https://www.web3sec.news/blog/cloud-iam-secrets-runbook</id><title>Cloud IAM and secrets: reduce standing access and prove revocation</title><link href="https://www.web3sec.news/blog/cloud-iam-secrets-runbook"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>An operating model for human roles, workload identities, secret consumers and emergency cloud access.</summary></entry><entry><id>https://www.web3sec.news/blog/production-data-backup-runbook</id><title>Production data and backups: prove you can recover without giving attackers a second copy</title><link href="https://www.web3sec.news/blog/production-data-backup-runbook"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>A runbook for database access, backup isolation, retention, restoration and safe evidence during data incidents.</summary></entry><entry><id>https://www.web3sec.news/blog/api-authorization-review-runbook</id><title>API authorization: test the actor, object and action together</title><link href="https://www.web3sec.news/blog/api-authorization-review-runbook"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>A practical review method for cross-tenant access, administrative functions, exports, background jobs and failure behavior.</summary></entry><entry><id>https://www.web3sec.news/blog/multisig-treasury-security-runbook</id><title>Multisig treasury operations: verify the transaction and every path around the threshold</title><link href="https://www.web3sec.news/blog/multisig-treasury-security-runbook"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>An operating runbook for signer independence, privileged transactions, modules, monitoring and recovery rehearsal.</summary></entry><entry><id>https://www.web3sec.news/blog/community-support-security-runbook</id><title>Community and support security: protect announcements without becoming a recovery scam</title><link href="https://www.web3sec.news/blog/community-support-security-runbook"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>Practical controls for moderators, bots, public links, support evidence and incident communications.</summary></entry><entry><id>https://www.web3sec.news/blog/ai-agent-mcp-security-runbook</id><title>AI agent and MCP security: constrain the tool, not just the prompt</title><link href="https://www.web3sec.news/blog/ai-agent-mcp-security-runbook"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>A runbook for agent integrations, local servers, authorization, data access and realistic prompt-injection tests.</summary></entry><entry><id>https://www.web3sec.news/blog/incident-evidence-runbook</id><title>Incident evidence: preserve what happened without spreading the breach</title><link href="https://www.web3sec.news/blog/incident-evidence-runbook"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>A procedure for first-response records, log exports, file provenance, access restrictions and investigative handoff.</summary></entry><entry><id>https://www.web3sec.news/blog/incident-tabletop-runbook</id><title>Incident tabletop: rehearse decisions while the systems are still healthy</title><link href="https://www.web3sec.news/blog/incident-tabletop-runbook"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>A repeatable exercise format for founders, engineering, security, support and the people authorized to stop operations.</summary></entry><entry><id>https://www.web3sec.news/blog/security-monitoring-runbook</id><title>Security monitoring: connect important events to an owner who can act</title><link href="https://www.web3sec.news/blog/security-monitoring-runbook"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>Build a small, testable detection system around identity changes, deployments, data access and treasury authority.</summary></entry><entry><id>https://www.web3sec.news/blog/frontend-third-party-script-security</id><title>Frontend security: review every script that can change what a user sees</title><link href="https://www.web3sec.news/blog/frontend-third-party-script-security"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>A practical review of browser code, tag managers and content security policies, including the interactions a successful build can still break.</summary></entry><entry><id>https://www.web3sec.news/blog/security-writing-evidence-review</id><title>Write a security finding someone else can verify</title><link href="https://www.web3sec.news/blog/security-writing-evidence-review"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>A review procedure for findings, incident narratives and technical articles: keep evidence, inference, recommendations and uncertainty separate.</summary></entry><entry><id>https://www.web3sec.news/blog/personal-ai-assistant-email-calendar-security</id><title>Connect an AI assistant to email and calendars without delegating your entire identity</title><link href="https://www.web3sec.news/blog/personal-ai-assistant-email-calendar-security"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>Decide what the assistant can read, draft, send and delete, then rehearse a malicious-message and disconnected-account scenario.</summary></entry><entry><id>https://www.web3sec.news/blog/financial-ai-agent-permission-boundaries</id><title>Financial AI agents: separate research, transaction preparation and execution authority</title><link href="https://www.web3sec.news/blog/financial-ai-agent-permission-boundaries"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>Design payment and treasury workflows around verified destinations, transaction-bound approvals, limits and an independent stop control.</summary></entry><entry><id>https://www.web3sec.news/blog/untrusted-repository-research-sandbox</id><title>Run unfamiliar research repositories without lending them your laptop’s credentials</title><link href="https://www.web3sec.news/blog/untrusted-repository-research-sandbox"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>Inspect before executing, isolate dependencies and tests, constrain network and filesystem access, and verify disposal with dummy secrets.</summary></entry><entry><id>https://www.web3sec.news/blog/ai-assisted-bug-bounty-workflow</id><title>AI-assisted bug bounty work: keep scope, execution and evidence under researcher control</title><link href="https://www.web3sec.news/blog/ai-assisted-bug-bounty-workflow"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>Use agents for understanding and reproducible reporting while preserving program authorization, data boundaries and meaningful human validation.</summary></entry><entry><id>https://www.web3sec.news/blog/mcp-server-installation-review</id><title>Before installing an MCP server: review the package, process and connected account separately</title><link href="https://www.web3sec.news/blog/mcp-server-installation-review"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>A preflight and change-review procedure for local and remote MCP integrations, from installation hooks to token revocation.</summary></entry><entry><id>https://www.web3sec.news/blog/agent-secrets-scope-and-recovery</id><title>Agent credentials: issue the smallest useful secret and prove you can revoke it</title><link href="https://www.web3sec.news/blog/agent-secrets-scope-and-recovery"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>An operating procedure for task-scoped identities, secret delivery, output review and recovery after unintended access or upload.</summary></entry><entry><id>https://www.web3sec.news/blog/browser-agent-session-security</id><title>Browser agents and logged-in sessions: protect the account behind the tab</title><link href="https://www.web3sec.news/blog/browser-agent-session-security"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>Review the authority inherited from cookies, browser profiles, connected sites and downloads before an agent uses an authenticated browser.</summary></entry><entry><id>https://www.web3sec.news/blog/agent-memory-retrieval-poisoning</id><title>Agent memory and RAG: prevent retrieved text from becoming persistent policy</title><link href="https://www.web3sec.news/blog/agent-memory-retrieval-poisoning"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>Track source provenance, enforce current retrieval permissions and test whether poisoned content survives into later tasks.</summary></entry><entry><id>https://www.web3sec.news/blog/agent-skills-plugin-review</id><title>Review agent skills and plugins as instructions, dependencies and delegated authority</title><link href="https://www.web3sec.news/blog/agent-skills-plugin-review"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>Inspect the whole instruction bundle, referenced resources and effective permissions before enabling a workflow extension or accepting its update.</summary></entry><entry><id>https://www.web3sec.news/blog/unattended-agent-schedules-and-budgets</id><title>Unattended agents: bound schedules, retries, cumulative usage and stale approvals</title><link href="https://www.web3sec.news/blog/unattended-agent-schedules-and-budgets"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>Make repeated agent work stop predictably when permissions, timing, costs or external side effects no longer match the approved task.</summary></entry><entry><id>https://www.web3sec.news/blog/agent-localhost-network-boundaries</id><title>Agents, localhost and internal networks: enforce what the executor can actually reach</title><link href="https://www.web3sec.news/blog/agent-localhost-network-boundaries"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>Protect local bridges, development services, cloud metadata and internal APIs with explicit network and application boundaries.</summary></entry><entry><id>https://www.web3sec.news/blog/scope-mobile-app-security-test</id><title>Scope a mobile security test: the app, the device and the API are separate boundaries</title><link href="https://www.web3sec.news/blog/scope-mobile-app-security-test"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>Prepare Android and iOS builds, device coverage, representative accounts and acceptance criteria so a mobile assessment answers a real release question.</summary></entry><entry><id>https://www.web3sec.news/blog/mobile-deep-links-session-boundaries</id><title>Mobile deep links: verify the destination without trusting the requested action</title><link href="https://www.web3sec.news/blog/mobile-deep-links-session-boundaries"/><updated>2026-11-08T00:00:00Z</updated><published>2026-11-08T00:00:00Z</published><summary>Review Android App Links, iOS universal links, custom schemes and exported entry points against account state, input validation and server authorization.</summary></entry></feed>