<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Vs-Code-Extension on CuraSec</title><link>https://curasec.metacog.co.kr/tags/vs-code-extension/</link><description>Recent content in Vs-Code-Extension on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 10 Aug 2026 11:57:16 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/vs-code-extension/index.xml" rel="self" type="application/rss+xml"/><item><title>Malicious Solidity Pro VS Code Extensions Harvest Wallets and Credentials</title><link>https://curasec.metacog.co.kr/insights/2026-08-10-solidity-pro-vs-code-extensions-steal-crypto-wallets-api-key/</link><pubDate>Mon, 10 Aug 2026 11:57:16 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-08-10-solidity-pro-vs-code-extensions-steal-crypto-wallets-api-key/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Act:&lt;/strong> If any developers on your team installed helper-beeps.solidity-pro or web3devtoolsx.solidity-pro, treat the workstation as compromised: remove the extensions, rotate all API keys and credentials accessible from that machine, and audit browser-stored secrets. Extend extension allow-listing policies to block unvetted publishers.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Act:&lt;/strong> Sweep developer endpoints for the presence of either extension directory (helper-beeps.solidity-pro, web3devtoolsx.solidity-pro) and review outbound network activity from developer machines for credential exfiltration since these extensions were available; the specific extension IDs give you a concrete hunt anchor.&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> A targeted supply-chain attack against Solidity/web3 developers via marketplace extensions; notable as a recurring pattern but operationally relevant only if your org employs blockchain developers, in which case delegate an extension audit to your engineering team.&lt;/li>
&lt;/ul></description></item></channel></rss>