flutter-api-reverse-engineering

Fail

Audited by Snyk on Jun 24, 2026

Risk Level: CRITICAL
Full Analysis

HIGH W007: Insecure credential handling detected in skill instructions.

  • Insecure credential handling detected (high risk: 1.00). The prompt explicitly instructs extracting JWTs, session tokens, and crypto keys (e.g., captured_jwt, captured_token, captured_sk, memory-extracted private keys) and then embedding those secrets verbatim into replay requests and standalone client code, which forces the LLM to handle/output sensitive secret values (high exfiltration risk).

CRITICAL E006: Malicious code pattern detected in skill scripts.

  • Malicious code pattern detected (high risk: 1.00). This is a high-risk, explicitly abusive guide: it provides step-by-step techniques to bypass TLS/certificate pinning, hook BoringSSL to capture plaintext HTTP, extract JWTs, session tokens, and private keys from memory (via Frida hooks and MemoryAccessMonitor), and replay/store those credentials to build standalone clients—facilitating clear data exfiltration and credential theft.

MEDIUM W013: Attempt to modify system services in skill instructions.

  • Attempt to modify system services in skill instructions detected (high risk: 1.00). The prompt explicitly instructs installing and running frida-server on a device, pushing files, using rooted devices, accessing protected app data, and hooking/bypassing TLS and crypto protections to extract keys and tokens—actions that bypass security mechanisms and modify the target machine/device state.

Issues (3)

W007
HIGH

Insecure credential handling detected in skill instructions.

E006
CRITICAL

Malicious code pattern detected in skill scripts.

W013
MEDIUM

Attempt to modify system services in skill instructions.

Audit Metadata
Risk Level
CRITICAL
Analyzed
Jun 24, 2026, 06:52 PM
Issues
3
Security Audit — snyk — flutter-api-reverse-engineering