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
aeondave/adaptixc2-devWeb y bug bounty

adaptixc2-dev

⁨Build, review, debug, package, and activate AdaptixC2 v2 extenders and AxScript UI: agent payload builders, listeners, services, plugin calls, lifecycle, axtool specs, source-contract checks, and verification. Use for authorized extension development, not live C2 operation.⁩

v2026.11.13-21cd5684 instalaciones+4 en 7 días39 EstrellasMITsincronizado hace 10 horas

Instalar

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

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install aeondave/adaptixc2-dev

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

FirmaFirmado, ed25519
vOuI3BWC7h…9pVM7aBA==La CLI comprueba el SHA-256 y la firma antes de escribir cualquier archivo.
Paquete2a48a06e…f9a483de
2a48a06ed4af…5f50f9a483de7 archivos · ⁦27.7 KB⁩
EscaneoMedio1 hallazgo
  • injection.no_confirmationreferences/teamserver-api.md:140
Ver el escaneo completo
Fuentegithub.com/AeonDave/malskill/tree/main/offensive-coding/adaptixc2-dev@21cd568

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

Develop against the checked-out source, not remembered v1 APIs or the public GitBook. Pin the exact source revision and working-tree contract changes; re-run the contract gate for every new task.

Verified source: AdaptixC2 commit a1a9cead, with the local AdaptixServer/go.mod selecting github.com/Adaptix-Framework/axc2/v2 v2.0.14; committed source selects v2.0.13. The server declares Go 1.26.5; contract probes used Go 1.27.1. Match the actual host toolchain and dependency graph when building plugins.

Start with the contract gate

From <adaptix-root>:

bash
git status --short --branch
git rev-parse HEAD
git diff -- AdaptixServer/go.mod AdaptixServer/go.sum
go -C AdaptixServer list -m github.com/Adaptix-Framework/axc2/v2
go -C AdaptixServer env GOVERSION
go -C AdaptixServer doc github.com/Adaptix-Framework/axc2/v2.PluginAgent
go -C AdaptixServer doc github.com/Adaptix-Framework/axc2/v2.PluginListener
go -C AdaptixServer doc github.com/Adaptix-Framework/axc2/v2.PluginService

If go.work references missing modules, use GOWORK=off for these module-only probes. This does not establish the host's shared dependency graph: verify or repair that graph before building a plugin.

Then inspect the implementation that owns the behavior being changed:

bash
rg -n "InitPlugin|plugin.Open|LoadPlugin" AdaptixServer
rg -n "GenerateUI|ListenerUI|InitService|data_handler" AdaptixClient AdaptixServer
rg -n "TsAgentBuild|BuildPayload|GenerateProfiles" AdaptixServer
rg -n "plugin_service_(command|wait)|plugin_(agent|listener)_command" AdaptixClient AdaptixServer

If the revision, local contract changes, or module version differs, treat every signature and lifecycle statement below as a hypothesis until re-verified.

Choose one extender boundary

Extender Owns Does not own
Agent payload configuration/build, task encoding, beat processing, restored session behavior client transport, build-channel close, final artifact delivery
Listener transport instance lifecycle and inbound agent traffic agent protocol semantics beyond delegation to its agent plugin
Service auxiliary server behavior, optional dock/dialog UI, service messages and bounded RPC core agent/listener lifecycle or implicit authorization

Keep the dependency direction one-way:

text
AxScript UI -> named bridge call -> plugin boundary -> domain logic -> explicit Teamserver port

Do not let UI JSON, listener configuration, task arguments, or callback bytes select filesystem paths, programs, routes, or storage namespaces without validation. Keep Adaptix types at the boundary and ordinary Go types in domain code.

For boundary ownership, lifecycle state machines, failure semantics, and concurrency, load architecture-and-lifecycle.md.

Route to the narrowest reference

Task Load when
plugin-patterns.md Implementing Go interfaces, agent restore/build, listener start/stop, service calls, or safe boundary adapters
axscript-patterns.md Building payload forms, listener forms, service docks/dialogs, event handlers, or UI-to-plugin interactions
axscript-api.md Checking an exact client bridge method, argument order, return shape, or server stub parity
teamserver-api.md Selecting Teamserver calls for atomic data updates, task correlation, framed transport accounting, hooks, endpoints, storage, or messaging
generator-details.md Creating templates/specs, building, installing, activating, or auditing axtool behavior

Load the parent first, then only the references required by the current subtask.

Implement a thin vertical slice

  1. Define the user-visible outcome and the failure state before coding.
  2. Record the exact Adaptix revision, axc2 module version, Go toolchain, build flags, and shared dependency versions.
  3. Isolate protocol/build/service logic from Plugin*, Teamserver, and AxScript adapters.
  4. Implement one end-to-end path: UI input -> validation -> plugin call -> result/error -> observable UI state.
  5. Add lifecycle cleanup and concurrency bounds before adding more commands.
  6. Verify activation from server logs and runtime catalogs; process readiness alone does not prove the extender loaded.

Use explicit schemas at every JSON boundary. Reject unknown operations, missing required fields, oversized inputs, invalid enum values, unsafe paths, and malformed byte frames. Return errors with operation context; never turn an unknown command into a successful zero value.

Non-negotiable runtime rules

  • Agent and service .axs files are evaluated by server-side Goja for command metadata and by the Qt client for real UI behavior; listener .axs is client-only on the verified baseline. Keep top-level code declarative and place UI effects in GenerateUI, ListenerUI, or InitService.
  • Agent state must be reconstructible by AgentRestore. The current server does not retain the callbacks returned by CreateAgent when creating a session.
  • AEAD session counters vs restore: transport-layer sequence counters are not part of what survives an AgentRestore. If an agent plugin keeps a session key and reuses seq=0 under the same key after a restore, that is an AEAD nonce reuse — catastrophic for the profile's confidentiality. Reconstruct state so a restore forces a key-epoch bump or a fresh session handshake (pattern verified in two extender implementations: on restore without live counter state, invalidate the epoch and require a new HELLO).
  • BuildPayload returns artifact bytes and a filename to its caller. The WebSocket path sends/closes the build channel; the synchronous path returns the artifact directly.
  • Listener Start can fail while the API call still completes with a stopped instance. Make Start restart-safe, Stop idempotent, and verify runtime status.
  • Plugin instances are shared. Assume Call, CallRPC, task handlers, hooks, and build callbacks can overlap.
  • A service RPC timeout does not cancel plugin work. Bound work independently and correlate asynchronous replies with a request ID.
  • Go plugins cannot be safely unloaded from the process. Registry removal is not resource teardown; design cleanup before supporting runtime unload.
  • Treat extender binaries and axtool specs as trusted code. Do not run unreviewed packages or mutable build inputs.

Wrong-type traps (axc2/v2 v2.0.14)

Verified against axc2/[email protected]/adaptix_struct.go and the in-tree beacon UI. Common misuses that compile but corrupt runtime state:

Field / constant Real type Trap
AgentData.Sleep, AgentData.Jitter uint Beacon sleep is seconds; jitter is a percentage. Preserve those units at the boundary.
AgentData.Pid, AgentData.Tid string Format from numeric sources with fmt.Sprintf("%v", ...); do not cast.
AgentData.Id and every agentId on Teamserver/Call/InternalHandler int64 Never a string. In JavaScript treat it as opaque string when it may exceed Number.MAX_SAFE_INTEGER.
OS_MAC (constant 3) int No OS_MACOS symbol exists.
PluginService interface with Call and CallRPC An implementation with only Call will not satisfy the loader type assertion.
config.yaml -> extender_file filename string Must equal the Makefile .so output byte-for-byte; a mismatch loads nothing and the server log is the only signal.

Verification gates

Run focused tests for pure domain code, then compile with the exact Teamserver toolchain and dependency graph. At minimum, exercise:

  • valid and malformed boundary input;
  • short/truncated frames before indexing or slicing;
  • concurrent builds/calls under the race detector where supported;
  • create/start -> pause -> resume -> full stop for listeners, plus partial-start failure cleanup;
  • create and restored-session behavior for agents;
  • success, plugin error, timeout, late result, and disconnect for service UI;
  • build failure cleanup and absence of duplicate artifact delivery;
  • cold-start activation and runtime catalog/UI visibility.

Before claiming completion:

bash
go test ./...
go test -race ./...
go vet ./...
rg -n "panic\(|log\.Fatal|os\.Exit" .

Use the race gate for Go/domain packages on a supported native target; it does not prove races across the host/plugin boundary. Also inspect the built .so, server profile entry, load logs, command catalogs, and the intended UI in a real client. Report skipped gates and upstream source failures separately from extender failures.

Delivery record

Record:

  • pinned Adaptix revision, axc2 version, Go version, build flags, and target OS/architecture;
  • extender type, init signature, owned resources, cleanup path, and concurrency policy;
  • AxScript entry points and bridge calls used;
  • package/spec provenance and activation path;
  • tests run, runtime evidence, known source limitations, and rollback/restart procedure.

Do not claim transactional install, safe hot reload, automatic timeout cancellation, or UI delivery without direct evidence from the pinned source and a runtime check.

Archivos de esta versión

Permisos

PermisoDeclaradoHallado en el escaneo
Lee archivosNoNo
Escribe archivosSíSí
Ejecuta comandos de shellSíSí
Usa la redNoNo
Usa conectoresSíSí
Controla un navegadorNoNo

Hallazgos del escaneo

Revisado el 13 nov 2026

  1. MediaPrompt injection · injection.no_confirmationreferences/teamserver-api.md:140

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

VersiónPublicadaCommitSHA-256FirmaCambio de permisos
v2026.11.13-21cd56813 nov 202621cd5682a48a06eFirmada–

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