<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>OpenAI ChatGPT Enterprise - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/openai-chatgpt-enterprise/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Fri, 06 Nov 2026 21:01:52 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/openai-chatgpt-enterprise/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>Detection of Cryptographic Hashes in Generative AI Prompts</title><link>https://feed.craftedsignal.io/briefs/2026-11-genai-hash-detection/</link><pubDate>Fri, 06 Nov 2026 21:01:52 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-genai-hash-detection/</guid><description>The security_ai integration for Elastic enables the detection of hex-encoded cryptographic hashes within GenAI prompts and completions, which may indicate credential exfiltration, offline cracking attempts, or encoded prompt injection payloads.</description><content:encoded><![CDATA[<p>The Elastic security_ai integration provides detection capabilities for identifying hex-encoded cryptographic digests (MD5, SHA-1, SHA-256, and SHA-512) within prompts sent to or completions returned by Generative AI services. The presence of these hashes in LLM interactions can serve as an indicator for several malicious activities: passing credential hashes for offline cracking, exfiltrating data fingerprints, or embedding encoded instructions as part of prompt injection payloads.</p>
<h2 id="investigation">Investigation</h2>
<p>Security teams should investigate flagged hashes by examining <code>security_ai.hash_string.input_messages.strings</code> and <code>security_ai.hash_string.output_messages.strings</code>. Analysis should include reviewing the full conversation context for references to usernames, credentials, or structured exfiltration payloads, and verifying if the hash corresponds to known-bad IOCs.</p>
<h2 id="false-positives">False Positives</h2>
<p>Legitimate workflows such as security/forensics tools conducting threat intelligence lookups or CI/CD pipelines utilizing git commit SHAs, Docker image digests, or package checksums may trigger this rule. Contextual review is required to verify the nature of the hash.</p>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>genai</category><category>exfiltration</category><category>cloud-security</category><category>machine-learning</category><category>Defense Evasion</category><category>LLM</category><category>Prompt Injection</category></item></channel></rss>