Saltar al contenido
Nuevo

DeepSeek V4.1 Flash gratis por 7 días: 10M tokens al día tras una recarga de $10 o más. Hasta el 30/11.

Cómo funciona
zhaoxuya520/competition-browser-persistenceWeb y bug bounty

competition-browser-persistence

⁨Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for browser cookies, localStorage, sessionStorage, IndexedDB, Cache Storage, service workers, offline caches, and client-side session persistence. Use when the user asks to inspect browser state, replay cached auth or sessi⁩

v2026.9.22-cab634b3 instalaciones+3 en 7 días44,8 mil EstrellasMITsincronizado hace 2 horas

Instalar

¿Aún no tienes la CLI de NotHoly? Instálala primero.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install zhaoxuya520/competition-browser-persistence

Escribe en ⁦~/.notholy/skills⁩ después de comprobar la firma y el SHA-256.

FirmaFirmado, ed25519
4O6fUXeKvB…D0Xyu0Ag==La CLI comprueba el SHA-256 y la firma antes de escribir cualquier archivo.
Paquete81b9023c…03dd19b5
81b9023cdcb8…053203dd19b53 archivos · ⁦2.1 KB⁩
EscaneoBajosin hallazgos
El escaneo no encontró nada que señalar en esta versión.Ver el escaneo completo
Fuentegithub.com/zhaoxuya520/reverse-skill/tree/main/CTF-Sandbox-Orchestrator/competition-browser-persistence@cab634b

Esta entrada todavía no está escrita en tu idioma, así que aparece en English.

Use this skill only as a downstream specialization after $ctf-sandbox-orchestrator is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to $ctf-sandbox-orchestrator first.

Use this skill when the decisive branch lives in browser-held state rather than only in visible HTML or backend source.

Reply in Simplified Chinese unless the user explicitly requests English.

Quick Start

  1. Identify the active persistence surface first: cookie jar, localStorage, sessionStorage, IndexedDB, Cache Storage, or service worker.
  2. Record origin, scope, domain, path, expiry, and key names before mutating state.
  3. Tie stored state to one concrete effect: request header, rendered branch, cached response, offline behavior, or hidden route access.
  4. Separate boot-time state from runtime-mutated state.
  5. Reproduce the smallest stateful sequence that reaches the decisive branch.

Workflow

1. Map Browser State Surfaces

  • Inspect cookies, storage buckets, service worker registrations, cache entries, and transient globals exposed during boot.
  • Record which origin, host, route, or feature flag each state item actually applies to.
  • Keep auth tokens, refresh material, CSRF state, cached responses, and feature toggles in separate evidence blocks.

2. Tie State To Runtime Behavior

  • Show how stored state becomes request headers, role derivation, route visibility, cached API data, or offline fallback behavior.
  • Compare clean-state and mutated-state runs with one variable changed at a time.
  • Distinguish UI-only state from backend-accepted state.

3. Reduce To The Decisive Persistence Chain

  • Compress the result to the smallest chain: initial page or login -> state persisted -> subsequent request or render branch -> resulting capability.
  • Keep extracted storage, service worker scripts, and replay steps tied to the same origin and route.
  • If the problem broadens into general web routing or worker behavior outside browser persistence, switch back to the broader web-runtime skill.

Read This Reference

  • Load references/browser-persistence.md for the browser-state checklist, service-worker checklist, and evidence packaging.

What To Preserve

  • Cookie attributes, storage keys, database names, cache keys, service worker scopes, and origin boundaries
  • The exact request or render effect caused by each decisive state item
  • Clean-state vs mutated-state reproduction steps for the smallest working path

Archivos de esta versión

Permisos

PermisoDeclaradoHallado en el escaneo
Lee archivosNoNo
Escribe archivosNoNo
Ejecuta comandos de shellNoNo
Usa la redNoNo
Usa conectoresNoNo
Controla un navegadorNoNo

Hallazgos del escaneo

Revisado el 13 nov 2026

El escaneo no encontró nada que señalar en esta versión.

Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.

VersiónPublicadaCommitSHA-256FirmaCambio de permisos
v2026.9.22-cab634b13 nov 2026cab634b81b9023cFirmada–

Pregunta todo lo que tu alcance permite.

Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.

  1. 1/3

    Crea la cuenta

    Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.

    IndividualEmpresa
  2. 2/3

    Añade créditos

    Con tarjeta. Pagas por token, sin suscripción.

    $5.00recarga mínima
  3. 3/3

    Pregunta

    En el chat, o instala el CLI y ejecuta notholy login en tu terminal.

    $ notholy login