AbbySec

My digital playground – where hacking meets learning.

View on GitHub
27 February 2026

SOC120 – Phishing Mail Detected (Internal to Internal) – False Positive

by

🧠 Summary

This alert involved a phishing detection rule triggered for an internal-to-internal email.

Upon investigation, no malicious indicators were identified. The email contained no attachments, no URLs, and no suspicious content. The SMTP source was an internal mail server.

The alert was classified as a False Positive.


🚨 Alert Details


πŸ” Phase 1 – Initial Email Parsing

The following details were reviewed during triage:


πŸ“„ Email Content Review

Email Body:

Hi Susie, Can we arrange a meeting today if you are available?

Evidence:

Email Snippet

Findings:

The content appears to be normal internal communication.


🌐 SMTP & Infrastructure Validation

The SMTP address:

172.16.20.3


πŸ§ͺ Artifact Analysis

No artifacts were identified.


βš–οΈ Investigation Conclusion

Category Result
Attachment None
Alert False Positive
Execution Not applicable
C2 Traffic Not applicable
Compromise No impact

The email was determined to be legitimate internal communication.


🧠 Key SOC Lessons

  1. Not every phishing alert represents malicious activity.
  2. Internal-to-internal emails require verification but not assumption.
  3. Unusual timing alone does not equal compromise.
  4. Proper triage prevents unnecessary escalation.
  5. Rule-based detections can generate false positives.

🎯 Final Verdict

βœ”οΈ False Positive
βœ”οΈ No malicious indicators
βœ”οΈ No compromise detected
βœ”οΈ Alert closed after validation


tags: