rudra-ravi/frida-skills

frida-anti-instrumentation

Analyze and bypass anti-Frida, anti-debugging, root or jailbreak checks, emulator checks, ptrace, port scans, module scans, and integrity checks.

First seen May 12, 2026

Installation

$ npx skills add rudra-ravi/frida-skills --skill frida-anti-instrumentation

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from rudra-ravi/frida-skills · top by installs.

npx skills add rudra-ravi/frida-skills

Browse all from rudra-ravi/frida-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 1
License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,187 B
  • docs SUMMARY.md 179 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 70 installs

SKILL.md

Frida Anti-Instrumentation

Use this skill when the app exits, hides behavior, blocks attach, or detects Frida/root/jailbreak/emulator/debugging.

Diagnosis Order

  1. Prove whether failure happens before or after Frida attaches.
  2. Use spawn mode for early checks.
  3. Log exits, process checks, file checks, property checks, and native anti-debug calls.
  4. Identify the specific detection before bypassing it.
  5. Keep only narrow hooks that change the detected condition.

Android Boundaries

Java.perform(() => {
  const Runtime = Java.use("java.lang.Runtime");
  Runtime.exec.overload("java.lang.String").implementation = function (cmd) {
    console.log("Runtime.exec", cmd);
    return this.exec(cmd);
  };
});

Common Java surfaces: File.exists, SystemProperties.get, Build.*, package manager queries, shell command execution, debugger checks, emulator properties.

Native Boundaries

for (const name of ["open", "access", "stat", "ptrace", "prctl", "connect"]) {
  try {
    const f = Module.getGlobalExportByName(name);
    Interceptor.attach(f, { onEnter() { console.log(name); } });
  } catch (_) {}
}

Common native surfaces: /proc, maps, task, frida, gum-js-loop, TCP port scans, ptrace, prctl, syscall, dlopen, checksum functions.

iOS Boundaries

Look for file checks, URL scheme checks, fork, ptrace, sysctl, csops, dyld image scans, suspicious library names, and jailbreak path lists.

Verification

  • The app reaches the previously blocked screen or behavior.
  • Logs show which detection hook fired.
  • Removing the hook restores the failure.
  • The final bypass does not mask unrelated errors or crash paths.

References