<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Web3-Security on CuraSec</title><link>https://curasec.metacog.co.kr/tags/web3-security/</link><description>Recent content in Web3-Security on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 01 Oct 2026 17:21:52 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/web3-security/index.xml" rel="self" type="application/rss+xml"/><item><title>MetaMask Discloses Active Infrastructure Incident, No Wallet Breach Confirmed</title><link>https://curasec.metacog.co.kr/insights/2026-10-01-metamask-security-incident-prompts-exit-of-affected-ethereum/</link><pubDate>Thu, 01 Oct 2026 17:21:52 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-01-metamask-security-incident-prompts-exit-of-affected-ethereum/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> MetaMask reports an active infrastructure incident but has not confirmed user wallet compromise or published technical details. Monitor for follow-up disclosure with IOCs or affected component specifics before taking action.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> Active incident with no published IOCs, attack vector, or TTPs available yet — nothing actionable for detection or hunting. Watch for a follow-on technical disclosure before building any detections.&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Ongoing infrastructure-level incident at a major crypto wallet provider with no confirmed user impact; if the organization has any Ethereum validator or Web3 DeFi exposure through MetaMask, confirm whether affected validators apply to you once more detail is published.&lt;/li>
&lt;/ul></description></item></channel></rss>