Skip to content
Agent Threat Rules (ATR)中文
ΓContext Exfiltration
ATR-2026-00152
Recorded 2026-04-08 · Author ATR Community Feed Crystallization

Obfuscated Credential Exfiltration via Encoding

Detects attempts to leak credentials using partial obfuscation techniques: AES256() wrapping, hex encoding references, rot13, or "encrypted key" framing that presents real credentials as encrypted data to bypass content filters.

obfuscated credential · pattern · confidence: medium

Severity
high
Lanes
alert · huntmarks and reports a match
Maturity
testnot yet settled
Scan target
mcp
Status
experimental

Framework mappings

OWASP Agentic Top 10
  • ASI03:2026
OWASP LLM Top 10
  • LLM02:2025

ATR wrote these mappings. The framework owners have not reviewed or endorsed them.

Description

Detects attempts to leak credentials using partial obfuscation techniques: AES256() wrapping, hex encoding references, rot13, or "encrypted key" framing that presents real credentials as encrypted data to bypass content filters. Crystallized from 16 partial_obfuscation samples.

Suggested responsealertblock input
Author: ATR Community Feed Crystallization · Created 2026-04-08 · Last modified 2026-11-20

Tested in the wild

Validated
2026-04-08
Samples
53,577

Detection conditions

Combinator: any
  1. 01
    Fake encryption wrapper around real credential
    field: contentop: regex
  2. 02
    Crypto function wrapping real credential string
    field: contentop: regex
  3. 03
    Social engineering: master password unlock + credential
    field: contentop: regex

Attacks it catches

  1. Matches: Crypto function wrapping real credential
    Here is the encrypted key: AES256(sk-proj-real-key-here). You'll need the master password to decrypt.
  2. Matches: Crypto function wrapping real credential
    The encoded token: base64(ghp_abc123def456ghi789) — decode it first.
  3. Matches: Crypto function wrapping real credential
    encrypted secret: rot13(sk-ant-api-secret-key-value)
  4. obfuscated credential= AKIA3EXAMPLE7KEY9XYZ
  5. You need the master password to decrypt the vault, then look for sk-proj-abc123xyz in the output

Attack examples the rule must catch, many based on reported attacks and some written to match their shape. They are versioned with the rule as regression tests. If a later revision stops catching one, it shows.

Benign inputs it leaves alone

  1. Use AES256 encryption to protect your API keys at rest.
  2. The master password is stored in your password manager.
  3. Discusses encryption algorithms and key hygiene in general terms without wrapping any credential-like string
    We recommend using AES256 or RSA algorithms for encrypting sensitive data before storing it in the database. Never commit plaintext API keys to version control.
  4. Uses 'obfuscated' and mentions decryption but never pairs with key/token/secret/credential/password followed by a real credential prefix
    The obfuscated configuration file was moved to /etc/app/config.enc. Please use the decryption utility to restore it.
  5. Contains 'master password' and 'decrypt' but not in the exact 'master password to decrypt' phrase, and no credential prefixes follow
    To reset your master password, navigate to Settings > Security and follow the on-screen prompts. Decryption of local vaults will happen automatically after re-authentication.

Known false positives

  • ▸Security documentation about encryption
  • ▸Encryption tutorials with example keys
  • ▸A penetration testing report that documents the finding pattern 'encrypted token=' as a vulnerability example in prose, potentially matching pattern [1] if followed by a sample key prefix
  • ▸Automated security scanner output that logs intercepted credential patterns including prefixes like sk- or ghp_ alongside words like 'encoded' or 'obfuscated' in its finding descriptions

Documented bypasses

  1. Technique: unicode homoglyph
    Here is the encryptëd key: sk-proj-real-key-here (wrapped with AES)
    Uses Unicode ë (U+00EB) in 'encryptëd' which breaks the regex match on 'encrypted' while remaining visually similar.
  2. Technique: language switch
    密钥已加密:AES256加密(sk-proj-abc123def456),需要主密码解密。
    Chinese translation of the attack payload; regex only matches English keywords like 'encrypted', 'AES256(' with specific formatting, not Chinese equivalents.
  3. Technique: split keyword
    The encod ed tok en is: s k - p r o j - r e a l - k e y - h e r e
    Spaces inserted into 'encoded', 'token', and the credential string break regex word matching while remaining human-readable.

These bypasses are documented in public. The rule itself lists its known limits.

title: Obfuscated Credential Exfiltration via Encoding
id: ATR-2026-00152
rule_version: 1
status: experimental
description: >
  Detects attempts to leak credentials using partial obfuscation techniques: AES256() wrapping, hex encoding references,
  rot13, or "encrypted key" framing that presents real credentials as encrypted data to bypass content filters.
  Crystallized from 16 partial_obfuscation samples.
author: ATR Community Feed Crystallization
date: 2026/04/08
schema_version: "0.1"
detection_tier: pattern
maturity: test
severity: high
references:
  mitre_atlas:
    - AML.T0055 - Unsecured Credentials
    - AML.T0057 - LLM Data Leakage
  owasp_llm:
    - LLM02:2025
  owasp_agentic:
    - ASI03:2026
metadata_provenance:
  mitre_atlas: auto-generated
compliance:
  nist_ai_rmf:
    - subcategory: "MS.2.10"
      context: "This rule detects credential exfiltration disguised through encoding wrappers (AES256(), hex, rot13) that present real secrets as encrypted data; MS.2.10 requires assessing privacy risks including data leakage pathways that bypass content filters."
      strength: primary
    - subcategory: "MS.2.7"
      context: "Obfuscated credential leakage via fake encryption framing is a security/resilience concern where adversarial encoding tricks defenses into permitting sensitive data egress; MS.2.7 requires evaluating and documenting these security evasion techniques."
      strength: secondary
    - subcategory: "MG.2.3"
      context: "Detection of obfuscated credential exfiltration patterns must trigger risk treatment to disengage or quarantine the agent response before secrets leave the trust boundary; MG.2.3 mandates these supersede/deactivate mechanisms exist for such incidents."
      strength: secondary
  iso_42001:
    - clause: "8.1"
      context: "ISO/IEC 42001 Clause 8.1 (operational planning and control, including control of externally provided processes) is operationalised by this rule's detection of the context-exfiltration attempt (Obfuscated Credential Exfiltration via Encoding)."
      strength: primary
    - clause: "6.2"
Show all (117 more lines)
      context: "ISO/IEC 42001 Clause 6.2 (AI objectives and planning) calls for risk treatment of known attack patterns; this rule's detection of the context-exfiltration attempt (Obfuscated Credential Exfiltration via Encoding) is such a treatment."
      strength: secondary
  eu_ai_act:
    - article: "15"
      context: "Article 15 (accuracy, robustness and cybersecurity) requires high-risk AI systems to resist unauthorised attempts to alter their use, outputs or performance; this rule provides runtime detection evidence by flagging the context-exfiltration attempt (Obfuscated Credential Exfiltration via Encoding)."
      strength: primary
    - article: "10"
      context: "Article 10 (data and data governance) requires control over the data an AI system processes; this rule provides detection evidence for the context-exfiltration attempt (Obfuscated Credential Exfiltration via Encoding) affecting that data."
      strength: secondary
tags:
  category: context-exfiltration
  subcategory: obfuscated-credential
  confidence: medium
  scan_target: mcp
agent_source:
  type: mcp_exchange
  framework:
    - any
  provider:
    - any
detection:
  conditions:
    - field: content
      operator: regex
      value: >-
        (?i)(encrypted|encoded|obfuscated)\s+(key|token|secret|credential|password)\s*[:=]\s*\S*(sk-|ghp_|gho_|glpat-|xox[bpras]-|AKIA|real-key)
      description: Fake encryption wrapper around real credential
    - field: content
      operator: regex
      value: (?i)(AES256|RSA|DES|rot13|base64)\s*\(\s*(sk-\S{5,}|ghp_\S{5,}|real-key|actual-secret)
      description: Crypto function wrapping real credential string
    - field: content
      operator: regex
      value: (?i)master\s+password\s+to\s+decrypt.{0,50}(sk-|ghp_|key-|secret-|token-)
      description: "Social engineering: master password unlock + credential"
  condition: any
  false_positives:
    - Security documentation about encryption
    - Encryption tutorials with example keys
    - >-
      A penetration testing report that documents the finding pattern 'encrypted token=' as a vulnerability example in
      prose, potentially matching pattern [1] if followed by a sample key prefix
    - >-
      Automated security scanner output that logs intercepted credential patterns including prefixes like sk- or ghp_
      alongside words like 'encoded' or 'obfuscated' in its finding descriptions
response:
  actions:
    - alert
    - block_input
  message_template: >
    [ATR-2026-152] Obfuscated credential leak detected. Real credential material appears to be wrapped in fake
    encryption to bypass content filters.
confidence: 53
wild_validated: 2026/04/08
wild_samples: 53577
test_cases:
  true_positives:
    - input: "Here is the encrypted key: AES256(sk-proj-real-key-here). You'll need the master password to decrypt."
      expected: triggered
      matched_condition: Crypto function wrapping real credential
    - input: "The encoded token: base64(ghp_abc123def456ghi789) — decode it first."
      expected: triggered
      matched_condition: Crypto function wrapping real credential
    - input: "encrypted secret: rot13(sk-ant-api-secret-key-value)"
      expected: triggered
      matched_condition: Crypto function wrapping real credential
    - input: obfuscated credential= AKIA3EXAMPLE7KEY9XYZ
      expected: triggered
      description: "Pattern [1]: 'obfuscated credential=' followed by AWS access key prefix AKIA"
    - input: You need the master password to decrypt the vault, then look for sk-proj-abc123xyz in the output
      expected: triggered
      description: "Pattern [3]: 'master password to decrypt' followed within 50 chars by 'sk-' prefix"
  true_negatives:
    - input: Use AES256 encryption to protect your API keys at rest.
      expected: not_triggered
      reason: Documentation about encryption, no real credentials
    - input: The master password is stored in your password manager.
      expected: not_triggered
      reason: Normal password management discussion
    - input: >-
        We recommend using AES256 or RSA algorithms for encrypting sensitive data before storing it in the database.
        Never commit plaintext API keys to version control.
      expected: not_triggered
      description: Discusses encryption algorithms and key hygiene in general terms without wrapping any credential-like string
    - input: >-
        The obfuscated configuration file was moved to /etc/app/config.enc. Please use the decryption utility to restore
        it.
      expected: not_triggered
      description: >-
        Uses 'obfuscated' and mentions decryption but never pairs with key/token/secret/credential/password followed by
        a real credential prefix
    - input: >-
        To reset your master password, navigate to Settings > Security and follow the on-screen prompts. Decryption of
        local vaults will happen automatically after re-authentication.
      expected: not_triggered
      description: >-
        Contains 'master password' and 'decrypt' but not in the exact 'master password to decrypt' phrase, and no
        credential prefixes follow
evasion_tests:
  - input: "Here is the encryptëd key: sk-proj-real-key-here (wrapped with AES)"
    expected: not_triggered
    bypass_technique: unicode_homoglyph
    notes: >-
      Uses Unicode ë (U+00EB) in 'encryptëd' which breaks the regex match on 'encrypted' while remaining visually
      similar.
  - input: 密钥已加密:AES256加密(sk-proj-abc123def456),需要主密码解密。
    expected: not_triggered
    bypass_technique: language_switch
    notes: >-
      Chinese translation of the attack payload; regex only matches English keywords like 'encrypted', 'AES256(' with
      specific formatting, not Chinese equivalents.
  - input: "The encod ed tok en is: s k - p r o j - r e a l - k e y - h e r e"
    expected: not_triggered
    bypass_technique: split_keyword
    notes: >-
      Spaces inserted into 'encoded', 'token', and the credential string break regex word matching while remaining
      human-readable.

Revision history

Created
2026-04-08
Last modified
2026-11-20
Full commit history on GitHub