testing-api-authentication-weaknesses

Detect API authentication weaknesses in JWT tokens and session lifecycle.

2|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/Acczdy/MoZiSec --skill testing-api-authentication-weaknesses
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-api-authentication-weaknesses
Source: https://github.com/Acczdy/MoZiSec/tree/main/api-security/.claude/skills/testing-api-authentication-weaknesses
Command: npx skills add https://github.com/Acczdy/MoZiSec --skill testing-api-authentication-weaknesses

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the detection and assessment of API authentication weaknesses by analyzing tokens, endpoints, and session lifecycle across services.

Core Features & Use Cases

  • Detects broken authentication vectors such as alg:none, weak JWT secrets, missing exp, and token leakage in URLs or logs.
  • Evaluates token revocation and refresh flows, account enumeration, and session management across REST APIs.
  • Provides workflow guidance for red-team style testing in development, staging, and security assessment scenarios.

Quick Start

Run the agent against your API base URL to begin automated authentication weakness testing and generate a report.

Frequently Asked Questions about testing-api-authentication-weaknesses

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test API authentication weaknesses like JWT alg:none and weak secrets?

You can test API authentication weaknesses by running an automated agent script against your API base URL to detect JWT alg:none vulnerabilities, weak secrets, missing expiration claims, and token leakage in URLs or logs.

Can I automate token revocation and session lifecycle testing for REST APIs?

Yes, you can automate token revocation and session lifecycle testing for REST APIs by analyzing token refresh flows, detecting token reuse scenarios, and evaluating account enumeration vulnerabilities across your development and staging environments.

What is the best way to detect JWT token leakage in API security testing?

The best way to detect JWT token leakage during API security testing is to automate the analysis of tokens, endpoints, and session data to identify sensitive tokens exposed in URLs or logs across REST and GraphQL services.

Does this API pentest tool work with GraphQL APIs or only REST endpoints?

This API authentication testing tool works with both GraphQL and REST APIs, analyzing tokens, endpoints, and session lifecycle across services to uncover broken authentication vectors in development and security assessment scenarios.

Do I need Python 3.x and requests to run automated JWT security testing?

Yes, you need Python 3.x and the included agent script to run automated JWT security testing, with the requests library serving as an optional dependency for executing network calls against your API base URL.

Why does my API authentication test report show account enumeration vulnerabilities?

API authentication test reports show account enumeration vulnerabilities when the automated analysis identifies endpoints that leak valid user information during token evaluation, session management, and authentication flow testing across services.