<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Srey Leak</title>
    <description>The latest articles on DEV Community by Srey Leak (@sreyleak-security).</description>
    <link>https://dev.to/sreyleak-security</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4177187%2F1ddf53f1-b7bf-4725-9413-270b8d88aca0.jpg</url>
      <title>DEV Community: Srey Leak</title>
      <link>https://dev.to/sreyleak-security</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/sreyleak-security"/>
    <language>en</language>
    <item>
      <title>Five red flags of crypto "recovery" scams</title>
      <dc:creator>Srey Leak</dc:creator>
      <pubDate>Mon, 12 Oct 2026 01:13:25 +0000</pubDate>
      <link>https://dev.to/sreyleak-security/five-red-flags-of-crypto-recovery-scams-1bo3</link>
      <guid>https://dev.to/sreyleak-security/five-red-flags-of-crypto-recovery-scams-1bo3</guid>
      <description>&lt;p&gt;After the June 2026 Polymarket frontend hack, the victims got their money back — and then the real scam started. DMs flooded in from "recovery specialists" who had watched the same on-chain transfers everyone else did.&lt;/p&gt;

&lt;p&gt;I teach scam-prevention workshops in Long Beach, and this pattern shows up in every language community I work with. Here are the five red flags I drill.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. They contact YOU.&lt;/strong&gt; Real support never initiates a DM. Polymarket, Coinbase, MetaMask — none of them cold-message users about stolen funds.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. They ask for a seed phrase or private key.&lt;/strong&gt; There is no legitimate reason for anyone to need it. Not for "verification", not for "safe-keeping", not to "recover" anything.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. They promise guaranteed recovery.&lt;/strong&gt; On-chain theft is not reversible by a third party. If someone claims otherwise, they are selling you a story.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. They manufacture urgency.&lt;/strong&gt; "Your funds expire in 24 hours." Urgency exists to stop you from checking.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5. Their links look official but aren't.&lt;/strong&gt; Check the domain character by character. Polymarket support does not live at polymarketsupport[.]xyz.&lt;/p&gt;

&lt;p&gt;One sentence to remember: Polymarket refunded every June-hack victim directly. No third party was ever needed — and none will ever be.&lt;/p&gt;

&lt;p&gt;I'm a security researcher, not a recovery service. I write guides: session keys, multilingual scam patterns, pre-trading checklists. Links on my profile.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.ethereum.org/en/security/" rel="noopener noreferrer"&gt;Learn more about crypto security&lt;/a&gt;&lt;/p&gt;

&lt;h1&gt;
  
  
  security #crypto #scams #polymarket
&lt;/h1&gt;

</description>
      <category>securitycryptoscamspolymarket</category>
    </item>
    <item>
      <title>Session Keys: the one Polymarket feature most traders ignore</title>
      <dc:creator>Srey Leak</dc:creator>
      <pubDate>Sun, 11 Oct 2026 21:31:32 +0000</pubDate>
      <link>https://dev.to/sreyleak-security/session-keys-the-one-polymarket-feature-most-traders-ignore-2ahh</link>
      <guid>https://dev.to/sreyleak-security/session-keys-the-one-polymarket-feature-most-traders-ignore-2ahh</guid>
      <description>&lt;p&gt;Most people sign every trade with their main wallet key. That's like carrying your house deed to the grocery store.&lt;/p&gt;

&lt;p&gt;Polymarket's Session Keys exist to solve exactly this: a scoped signer with limited permissions, so your master key stays cold. At Coinbase, account-takeover incidents almost always started the same way — a hot key with too much power, phished once.&lt;/p&gt;

&lt;p&gt;Three rules I follow:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Trading key != storage key. Never mix them.&lt;/li&gt;
&lt;li&gt;The key that signs daily trades should hold only what you can afford to lose this week.&lt;/li&gt;
&lt;li&gt;Hardware wallet for anything long-term. Browser extensions are for convenience, not custody.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;None of this is exotic. It's boring hygiene — the kind that saves accounts.&lt;/p&gt;

&lt;p&gt;(Full breakdown coming in my next post: how to set up scoped signers step by step.)&lt;/p&gt;

&lt;p&gt;Not financial advice. Security is your responsibility.&lt;/p&gt;

</description>
      <category>security</category>
      <category>phishing</category>
      <category>scam</category>
      <category>cryptocurrency</category>
    </item>
  </channel>
</rss>
