Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
zhaoxuya520/competition-queue-worker-driftMalware and ransomware analysis

competition-queue-worker-drift

⁨Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for queues, async workers, cron jobs, delayed tasks, retry behavior, worker-only config drift, and payload-to-side-effect chains. Use when the user asks to trace a queue payload, inspect async job execution, explain worker-⁩

v2026.9.22-cab634b3 installs+3 in 7 days44.8K StarsMITsynced yesterday

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install zhaoxuya520/competition-queue-worker-drift

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
kuDRy9nvka…ZVaGlhDQ==The CLI checks the SHA-256 and the signature before it writes a file.
Package76d21636…57c75575
76d216362e55…887857c755753 files · ⁦2.0 KB⁩
ScanLowno findings
The scan found nothing to flag in this version.See the full scan
Sourcegithub.com/zhaoxuya520/reverse-skill/tree/main/CTF-Sandbox-Orchestrator/competition-queue-worker-drift@cab634b

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 effect happens after enqueue, inside a worker, or only under async runtime state that differs from the request path.

Reply in Simplified Chinese unless the user explicitly requests English.

Quick Start

  1. Map the async chain first: enqueue point, queue payload, worker consumer, retries, and final side effect.
  2. Keep request-time state separate from worker-time state.
  3. Record queue name, message shape, worker config, retry policy, and downstream store in one chain.
  4. Compare synchronous path and async path when behavior diverges.
  5. Reproduce the smallest enqueue-to-side-effect flow that proves the decisive async drift.

Workflow

1. Map Enqueue And Worker Identity

  • Record queue names, topics, cron schedules, delayed jobs, dead-letter queues, worker processes, and consumer groups.
  • Note which config, env vars, feature flags, or credentials exist only in the worker environment.
  • Keep enqueue request, stored payload, and worker identity tied together.

2. Trace Worker-Only State And Retries

  • Show how worker runtime differs from the request path: different env, files, mounts, caches, permissions, or clocks.
  • Record retry count, backoff, dedupe keys, failure handling, dead-letter flow, and idempotency behavior.
  • Distinguish immediate request success from eventual worker success or failure.

3. Reduce To The Decisive Async Chain

  • Compress the result to the smallest sequence: enqueue -> worker runtime -> retry or branch -> resulting effect.
  • State clearly whether the decisive difference lives in payload shape, worker config, retry path, or downstream consumer.
  • If the issue is really about the file parser invoked by the worker, switch back to the tighter file-parser skill.

Read This Reference

  • Load references/queue-worker-drift.md for the queue checklist, retry checklist, and evidence packaging.

What To Preserve

  • Queue names, payloads, worker identities, retry metadata, dead-letter edges, and downstream effects
  • The exact worker-only config or state that changes behavior
  • One minimal enqueue-to-side-effect reproduction chain

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsNoNo
Uses the networkNoNo
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

The scan found nothing to flag in this version.

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.9.22-cab634bNov 13, 2026cab634b76d21636Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login