<?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: Art Akopian</title>
    <description>The latest articles on DEV Community by Art Akopian (@artbanrox).</description>
    <link>https://dev.to/artbanrox</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%2F4246587%2F099863c5-c515-464e-8720-2f5ee65cc245.jpg</url>
      <title>DEV Community: Art Akopian</title>
      <link>https://dev.to/artbanrox</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/artbanrox"/>
    <language>en</language>
    <item>
      <title>A scam email from the real Google</title>
      <dc:creator>Art Akopian</dc:creator>
      <pubDate>Sun, 15 Nov 2026 21:51:22 +0000</pubDate>
      <link>https://dev.to/artbanrox/a-scam-email-from-the-real-google-4l3k</link>
      <guid>https://dev.to/artbanrox/a-scam-email-from-the-real-google-4l3k</guid>
      <description>&lt;p&gt;Last year a phishing email showed up from &lt;a href="mailto:no-reply@google.com"&gt;no-reply@google.com&lt;/a&gt;. It wasn't a lookalike address. It was the real one, and it passed Google's own signature check.&lt;/p&gt;

&lt;p&gt;The scammers got Google's system to send a real, signed message, then forwarded it on. Google first said that was working as intended. Later it said it was working on a fix.&lt;/p&gt;

&lt;p&gt;So checking the sender isn't enough anymore.&lt;/p&gt;

&lt;p&gt;Judge the message by what it asks you to do. If it wants you to sign in through a link, call a number in the email, or pay a new account, don't. Go to the site or app yourself.&lt;/p&gt;

&lt;p&gt;Source: &lt;a href="https://www.bleepingcomputer.com/news/security/phishers-abuse-google-oauth-to-spoof-google-in-dkim-replay-attack/" rel="noopener noreferrer"&gt;BleepingComputer, Apr 20, 2025 (news report)&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>security</category>
      <category>cybersecurity</category>
      <category>phishing</category>
      <category>email</category>
    </item>
    <item>
      <title>The scam email that comes "from" your own company</title>
      <dc:creator>Art Akopian</dc:creator>
      <pubDate>Sun, 15 Nov 2026 21:51:21 +0000</pubDate>
      <link>https://dev.to/artbanrox/the-scam-email-that-comes-from-your-own-company-54i2</link>
      <guid>https://dev.to/artbanrox/the-scam-email-that-comes-from-your-own-company-54i2</guid>
      <description>&lt;p&gt;Some scam emails look like they came from inside your own company. They use the same domain and format as the payroll notices.&lt;/p&gt;

&lt;p&gt;Microsoft 365 has a feature called Direct Send. It lets printers and apps email staff using the company's address. Microsoft says it "does not require any form of authentication." Scammers can use it too.&lt;/p&gt;

&lt;p&gt;Microsoft added a switch to block it in April 2025. It's off by default, so someone has to turn it on.&lt;/p&gt;

&lt;p&gt;If you run a company on Microsoft 365, ask your IT person this week whether RejectDirectSend is on. If an internal email asks you to change bank details, call the person on a number you already have.&lt;/p&gt;

&lt;p&gt;Source: &lt;a href="https://techcommunity.microsoft.com/blog/exchange/introducing-more-control-over-direct-send-in-exchange-online/4408790" rel="noopener noreferrer"&gt;Microsoft Exchange Team Blog, Apr 28, 2025 (updated May 20, 2026)&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>security</category>
      <category>cybersecurity</category>
      <category>phishing</category>
      <category>email</category>
    </item>
    <item>
      <title>Your bank's email can be faked, and still follow the rules</title>
      <dc:creator>Art Akopian</dc:creator>
      <pubDate>Sun, 15 Nov 2026 21:51:20 +0000</pubDate>
      <link>https://dev.to/artbanrox/your-banks-email-can-be-faked-and-still-follow-the-rules-5dk7</link>
      <guid>https://dev.to/artbanrox/your-banks-email-can-be-faked-and-still-follow-the-rules-5dk7</guid>
      <description>&lt;p&gt;Most people think email from a bank can't be faked. It can.&lt;/p&gt;

&lt;p&gt;There's a setting called DMARC. It tells inboxes what to do with mail that pretends to be from a company. It has three options: block it, send it to spam, or do nothing.&lt;/p&gt;

&lt;p&gt;Gmail's rules for big senders say a company has to have DMARC. But the setting is allowed to be "none," which means do nothing. That still counts as following the rules.&lt;/p&gt;

&lt;p&gt;So a bank can be fully compliant and someone can still send you fake mail in its name.&lt;/p&gt;

&lt;p&gt;Don't click links in bank emails. Open the app yourself.&lt;/p&gt;

&lt;p&gt;Source: &lt;a href="https://support.google.com/a/answer/81126" rel="noopener noreferrer"&gt;Google, Email sender guidelines (in force since Feb 1, 2024)&lt;/a&gt;; &lt;a href="https://www.cisa.gov/news-events/directives/bod-18-01-enhance-email-and-web-security" rel="noopener noreferrer"&gt;CISA BOD 18-01 on p=none vs p=reject&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>security</category>
      <category>cybersecurity</category>
      <category>phishing</category>
      <category>email</category>
    </item>
  </channel>
</rss>
