================================================================================ EMAIL 1: LEGITIMATE TRANSACTIONAL EMAIL (GitHub) Notes: Valid SPF, DKIM, and DMARC alignment. Consistent sending infrastructure. ================================================================================ Return-Path: Delivered-To: analyst@examplecorp.com Received: from mail-yw1-f173.google.com (mail-yw1-f173.google.com [209.85.128.173]) by mx.examplecorp.com with ESMTPS id x12si849201ywr.412.2026.11.20.08.15.22 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 20 Nov 2026 08:15:23 -0800 (PST) Received: by mail-yw1-f173.google.com with SMTP id 00721157ae682-6e1a2b3c4d5e for ; Fri, 20 Nov 2026 08:15:22 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1795191322; cv=none; d=google.com; s=arc-20240605; b=k9L2mP8qR4tV7wX1zY3bN6cM9vB2nK5jH8gF4dS1aQ7wE0rT3yU6iO9pL2kJ5hG8fD== Authentication-Results: mx.examplecorp.com; dkim=pass header.i=@github.com header.s=pf2023 header.b=aB3cD4eF; spf=pass (mx.examplecorp.com: domain of noreply@github.com designates 209.85.128.173 as permitted sender) smtp.mailfrom=noreply@github.com; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=github.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2023; t=1795191321; bh=9x8y7z6w5v4u3t2s1r0q9p8o7n6m5l4k3j2i1h0g=; h=Date:From:To:Subject:From; b=aB3cD4eF5gH6iJ7kL8mN9oP0qR1sT2uV3wX4yZ5aB6cD7eF8gH9iJ0kL1mN2oP3qR== Date: Fri, 20 Nov 2026 08:15:20 -0800 From: GitHub To: analyst@examplecorp.com Message-ID: <673d4e5f6a7b8_1234567890@github.com> Subject: [GitHub] A new SSH key was added to your account MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Hi analyst, The following SSH key was added to your account... ================================================================================ EMAIL 2: CREDENTIAL PHISHING / TYPOSQUATTING (Fake Microsoft 365 Alert) Notes: Uses a lookalike domain (rnicrosoft-security.com), fails DMARC alignment, and originates from an unassociated VPS IP. ================================================================================ Return-Path: Delivered-To: analyst@examplecorp.com Received: from server104.promo-mailer-vps.net (unknown [185.220.101.44]) by mx.examplecorp.com with ESMTP id m99si112233abc.10.2026.11.20.09.42.10 for ; Fri, 20 Nov 2026 09:42:11 -0800 (PST) Authentication-Results: mx.examplecorp.com; dkim=none; spf=pass (mx.examplecorp.com: domain of bounce-8842@promo-mailer-vps.net designates 185.220.101.44 as permitted sender) smtp.mailfrom=bounce-8842@promo-mailer-vps.net; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=rnicrosoft-security.com Date: Fri, 20 Nov 2026 17:42:08 +0000 From: "Microsoft 365 Security" Reply-To: To: analyst@examplecorp.com Message-ID: <20261120174208.99812@server104.promo-mailer-vps.net> Subject: URGENT: Unusual sign-in activity detected - Action Required X-Mailer: PHPMailer 6.5.0 MIME-Version: 1.0 Content-Type: text/html; charset=UTF-8

We detected an unrecognized login from Moscow, Russia. Verify your identity immediately to prevent account suspension.

================================================================================ EMAIL 3: BUSINESS EMAIL COMPROMISE (BEC) / CEO FRAUD Notes: Display name spoofing combined with a mismatched Reply-To address. Sent from a free webmail provider rather than the corporate domain. ================================================================================ Return-Path: Delivered-To: finance@examplecorp.com Received: from mail-sor-f41.google.com (mail-sor-f41.google.com [209.85.220.41]) by mx.examplecorp.com with ESMTPS id z44si556677def.88.2026.11.20.11.05.33 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 20 Nov 2026 11:05:34 -0800 (PST) Authentication-Results: mx.examplecorp.com; dkim=pass header.i=@gmail.com header.s=20230601 header.b=xYz98765; spf=pass (mx.examplecorp.com: domain of exec.director.9921@gmail.com designates 209.85.220.41 as permitted sender) smtp.mailfrom=exec.director.9921@gmail.com; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Date: Fri, 20 Nov 2026 11:05:31 -0800 From: "Sarah Jenkins (CEO)" Reply-To: To: finance@examplecorp.com Message-ID: Subject: Quick wire transfer needed before 2 PM X-Originating-IP: [41.234.12.89] MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Are you at your desk? I am in a confidential board meeting and need you to process an urgent vendor payment today. Reply with your cell number. ================================================================================ EMAIL 4: DIRECT DOMAIN SPOOFING WITH MALWARE ATTACHMENT Notes: Directly forges the internal domain (examplecorp.com). Fails both SPF and DKIM, triggering a DMARC failure. Contains a suspicious archive attachment. ================================================================================ Return-Path: Delivered-To: analyst@examplecorp.com Received: from [192.168.1.45] (helo=WIN-987654321) by mail.bulletproof-host.ru with ESMTP id 1a2B3c-000456-78 for ; Fri, 20 Nov 2026 14:20:01 +0300 Received: from mail.bulletproof-host.ru (mail.bulletproof-host.ru [91.200.14.88]) by mx.examplecorp.com with ESMTP id q77si334455ghi.21.2026.11.20.03.20.05 for ; Fri, 20 Nov 2026 03:20:06 -0800 (PST) Authentication-Results: mx.examplecorp.com; dkim=fail reason="signature verification failed" header.d=examplecorp.com; spf=fail (mx.examplecorp.com: domain of hr-payroll@examplecorp.com does not designate 91.200.14.88 as permitted sender) smtp.mailfrom=hr-payroll@examplecorp.com; dmarc=fail (p=QUARANTINE sp=QUARANTINE dis=QUARANTINE) header.from=examplecorp.com Date: Fri, 20 Nov 2026 14:19:58 +0300 From: "HR & Payroll" To: analyst@examplecorp.com Message-ID: <001a01db3b5c$8899aabb$99ccbbaa$@examplecorp.com> Subject: Updated Q4 Bonus & Salary Schedule X-Priority: 1 (Highest) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_001B_01DB3B75.AE123450" ------=_NextPart_000_001B_01DB3B75.AE123450 Content-Type: text/plain; charset="us-ascii" Please review the attached encrypted document for your Q4 compensation adjustments. Password: 2026 ------=_NextPart_000_001B_01DB3B75.AE123450 Content-Type: application/zip; name="Q4_Bonus_Schedule.zip" Content-Disposition: attachment; filename="Q4_Bonus_Schedule.zip" Content-Transfer-Encoding: base64 UEsDBBQAAAAIA... [TRUNCATED MALICIOUS PAYLOAD] ... ================================================================================ EMAIL 5: LEGITIMATE MARKETING NEWSLETTER (Via Third-Party ESP) Notes: Return-Path differs from the From header (standard for Mailchimp/SendGrid), but SPF passes for the bounce domain and DKIM passes for the brand domain, satisfying DMARC alignment. ================================================================================ Return-Path: Delivered-To: analyst@examplecorp.com Received: from mail142.atl21.rsgsv.net (mail142.atl21.rsgsv.net [198.2.138.142]) by mx.examplecorp.com with ESMTPS id p11si998877jkl.55.2026.11.20.13.00.12 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 20 Nov 2026 13:00:13 -0800 (PST) Authentication-Results: mx.examplecorp.com; dkim=pass header.i=@securityweekly.io header.s=k1 header.b=mN4oP5qR; spf=pass (mx.examplecorp.com: domain of bounce-mc.us19_98765432.123456-analyst=examplecorp.com@mail142.atl21.rsgsv.net designates 198.2.138.142 as permitted sender) smtp.mailfrom=bounce-mc.us19_98765432.123456-analyst=examplecorp.com@mail142.atl21.rsgsv.net; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=securityweekly.io DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=securityweekly.io; s=k1; t=1795208410; bh=1a2b3c4d5e6f7g8h9i0j1k2l3m4n5o6p7q8r9s0t=; h=Subject:From:Reply-To:To:Date:Message-ID:List-Unsubscribe; b=mN4oP5qR6sT7uV8wX9yZ0aB1cD2eF3gH4iJ5kL6mN7oP8qR9sT0uV1wX2yZ3aB4c== Date: Fri, 20 Nov 2026 21:00:10 +0000 From: "Security Weekly Digest" Reply-To: "Security Weekly Digest" To: Message-ID: <9876543210abcdef.20261120210010@mail142.atl21.rsgsv.net> List-Unsubscribe: , Subject: Weekly Threat Intelligence Briefing - Issue #412 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Welcome to this week's threat intelligence roundup...