Back to catalog
Static reviewDevelopment

Skill dossier

performing-jwt-none-algorithm-attack

Source declaration

Execute and test the JWT none algorithm attack, crafting tokens with the alg header set to none using PyJWT and an intercepting proxy (Burp Suite/mitmproxy) to bypass signature verification and forge arbitrary claims. Use during authorized penetration tests or security assessments of applications that use JWT for authentication or authorization, to validate that the server rejects unsigned tokens.

The author's original description, preserved in English. It describes intent, not verified performance.

Execute and test the JWT none algorithm attack, crafting tokens with the alg header set to none using PyJWT and an intercepting proxy (Burp Suite/mitmproxy) to bypass signature verification and forge arbitrary claims. Use during authorized penetration tests or security assessments of applications that use JWT for authentication or authorization, to validate that the server rejects unsigned tokens.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Execute and test the JWT none algorithm attack, crafting tokens with the alg header set to none using PyJWT and an intercepting proxy (Burp Suite/mitmproxy) to bypass signature verification and forge arbitrary claims. Use during authorized penetration tests or security assessments of applications that use JWT for authentication or authorization, to validate that the server rejects unsigned tokens. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Step 1: Capture a Valid JWT [Source statement; provisional, not tested. Evidence: skills/performing-jwt-none-algorithm-attack/SKILL.md:L74]
  • Step 2: Decode and Analyze the Token [Source statement; provisional, not tested. Evidence: skills/performing-jwt-none-algorithm-attack/SKILL.md:L82]
  • Step 3: Craft a Forged Token with None Algorithm [Source statement; provisional, not tested. Evidence: skills/performing-jwt-none-algorithm-attack/SKILL.md:L103]
  • Step 4: Additional JWT Attack Variants [Source statement; provisional, not tested. Evidence: skills/performing-jwt-none-algorithm-attack/SKILL.md:L285]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/performing-jwt-none-algorithm-attack/SKILL.md:L1-L33]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
4
Markdown files
2
scripts
1
references
1
Size
31.7 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/performing-jwt-none-algorithm-attack/LICENSEOther11 KB
skills/performing-jwt-none-algorithm-attack/references/api-reference.mdReference1.7 KB
skills/performing-jwt-none-algorithm-attack/scripts/agent.pyScript6.9 KB
skills/performing-jwt-none-algorithm-attack/SKILL.mdInstruction12.1 KB

SKILL.md frontmatter

{
  "name": "performing-jwt-none-algorithm-attack",
  "description": "Execute and test the JWT none algorithm attack, crafting tokens with the alg header set to none using PyJWT and an intercepting proxy (Burp Suite/mitmproxy) to bypass signature verification and forge arbitrary claims. Use during authorized penetration tests or security assessments of applications that use JWT for authentication or authorization, to validate that the server rejects unsigned tokens.",
  "domain": "cybersecurity",
  "subdomain": "api-security",
  "tags": [
    "jwt",
    "none-algorithm",
    "authentication-bypass",
    "token-manipulation",
    "signature-bypass",
    "penetration-testing",
    "owasp",
    "web-security"
  ],
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "PR.PS-01",
    "ID.RA-01",
    "PR.DS-10",
    "DE.CM-01"
  ],
  "mitre_attack": [
    "T1190",
    "T1059.007",
    "T1552.001",
    "T1027",
    "T1070"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Action

    Overview

    Source-described action candidate under “Overview”; not verified execution.

  2. 02
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  3. 03
    Action

    JWT Structure

    Source-described action candidate under “JWT Structure”; not verified execution.

  4. 04
    Action

    Attack Methodology

    Source-described action candidate under “Attack Methodology”; not verified execution.

  5. 05
    Action

    Step 1: Capture a Valid JWT

    Source-described action candidate under “Step 1: Capture a Valid JWT”; not verified execution.

  6. 06
    Action

    Step 2: Decode and Analyze the Token

    Source-described action candidate under “Step 2: Decode and Analyze the Token”; not verified execution.

Inspect all extracted workflow candidates (15 candidate steps)
  1. 07
    Action

    Step 3: Craft a Forged Token with None Algorithm

    Source-described action candidate under “Step 3: Craft a Forged Token with None Algorithm”; not verified execution.

  2. 08
    Action

    Step 4: Additional JWT Attack Variants

    Source-described action candidate under “Step 4: Additional JWT Attack Variants”; not verified execution.

  3. 09
    Decision

    If the server uses RS256 (asymmetric), an attacker who knows the public key can:

    Source-described decision candidate under “Step 4: Additional JWT Attack Variants”; not verified execution.

  4. 10
    Action

    Change `alg` to `HS256`

    Source-described action candidate under “Step 4: Additional JWT Attack Variants”; not verified execution.

  5. 11
    Action

    Sign the token using the public key as the HMAC secret

    Source-described action candidate under “Step 4: Additional JWT Attack Variants”; not verified execution.

  6. 12
    Action

    The server may verify the signature using its public key as an HMAC key

    Source-described action candidate under “Step 4: Additional JWT Attack Variants”; not verified execution.

  7. 13
    Action

    Mitigation Strategies

    Source-described action candidate under “Mitigation Strategies”; not verified execution.

  8. 14
    Action

    Detection Indicators

    Source-described action candidate under “Detection Indicators”; not verified execution.

  9. 15
    Action

    References

    Source-described action candidate under “References”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Items warrant review

31 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Medium

Network access is mentioned

11 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 11 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

20 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 20 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/performing-jwt-none-algorithm-attack/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 4 collected file(s), 2 Markdown file(s), and 1 script file(s), enabling source-level inspection. [Evidence: skills/performing-jwt-none-algorithm-attack/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/performing-jwt-none-algorithm-attack
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.