Pular para o conteúdo
Novo

DeepSeek V4.1 Flash grátis por 7 dias: 10M tokens por dia após recarga de $10 ou mais. Até 30/11.

Como funciona
hlnd2t/find-cnetworkmessages-vtable-decompilesEngenharia reversa e fuzzing

find-CNetworkMessages_vtable-decompiles

⁨Find and identify CNetworkMessages_AllowAdditionalMessageRegistration and CNetworkMessages_IsAdditionalMessageRegistrationAllowed virtual functions in CS2 binary using IDA Pro MCP. Use this skill when reverse engineering CS2 networksystem.dll or libnetworksystem.so to locate both vfuncs by reusing t⁩

v2026.11.13-dcf20203 instalações+3 em 7 dias67 EstrelasMITsincronizado há 11 horas

Instalar

Ainda não tem a CLI da NotHoly? Instale primeiro.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install hlnd2t/find-cnetworkmessages-vtable-decompiles

Grava em ⁦~/.notholy/skills⁩ depois de conferir a assinatura e o SHA-256.

AssinaturaAssinado, ed25519
nCJ9XKkn/S…BKCXF/CQ==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacote8c3f30d8…82a0c5cd
8c3f30d84fef…797d82a0c5cd1 arquivo · ⁦2.0 KB⁩
VarreduraBaixonenhum achado
A varredura não encontrou nada para apontar nesta versão.Ver a varredura completa
Fontegithub.com/HLND2T/CS2_VibeSignatures/tree/main/.claude/skills/find-CNetworkMessages_vtable-decompiles@dcf2020

Este item ainda não foi escrito no seu idioma, então aparece em English.

Locate CNetworkMessages_AllowAdditionalMessageRegistration and CNetworkMessages_IsAdditionalMessageRegistrationAllowed vfuncs in CS2 networksystem.dll or libnetworksystem.so using IDA Pro MCP tools.

Method

1. Load CNetworkMessages_RegisterNetworkFieldChangeCallbackInternal from YAML

ALWAYS Use SKILL /get-func-from-yaml with func_name=CNetworkMessages_RegisterNetworkFieldChangeCallbackInternal.

If the skill returns an error, STOP and report to user.

Otherwise, extract:

  • vfunc_index of CNetworkMessages_RegisterNetworkFieldChangeCallbackInternal
  • vfunc_offset of CNetworkMessages_RegisterNetworkFieldChangeCallbackInternal

2. Load CNetworkMessages VTable from YAML

ALWAYS Use SKILL /get-vtable-from-yaml with class_name=CNetworkMessages.

If the skill returns an error, STOP and report to user.

Otherwise, extract:

  • vtable_numvfunc
  • vtable_entries

3. Resolve the Two Adjacent Slots

Compute the candidate slots:

  • allow_vfunc_index = CNetworkMessages_RegisterNetworkFieldChangeCallbackInternal.vfunc_index + 1
  • allow_vfunc_offset = CNetworkMessages_RegisterNetworkFieldChangeCallbackInternal.vfunc_offset + 8
  • isallowed_vfunc_index = CNetworkMessages_RegisterNetworkFieldChangeCallbackInternal.vfunc_index + 2
  • isallowed_vfunc_offset = CNetworkMessages_RegisterNetworkFieldChangeCallbackInternal.vfunc_offset + 16

Validate that isallowed_vfunc_index < vtable_numvfunc, then read:

  • allow_func_addr = CNetworkMessages_vtable[allow_vfunc_index]
  • isallowed_func_addr = CNetworkMessages_vtable[isallowed_vfunc_index]

This adjacent-slot rule is required because AllowAdditionalMessageRegistration and IsAdditionalMessageRegistrationAllowed immediately follow RegisterNetworkFieldChangeCallbackInternal in the CNetworkMessages vtable.

4. Decompile Both Candidate Functions

Decompile both candidates:

text
mcp__ida-pro-mcp__decompile addr="<allow_func_addr>"
mcp__ida-pro-mcp__decompile addr="<isallowed_func_addr>"

Confirm allow_func_addr is the simple byte setter pattern:

c
void __fastcall sub_18009B330(__int64 a1, char a2)
{
  *(_BYTE *)(a1 + 1372) = a2;
}

Windows assembly example:

asm
mov     [rcx+55Ch], dl
retn

Then confirm isallowed_func_addr is the matching byte getter using the same member offset:

c
__int64 __fastcall sub_18009B340(__int64 a1)
{
  return *(unsigned __int8 *)(a1 + 1372);
}

Windows assembly example:

asm
movzx   eax, byte ptr [rcx+55Ch]
retn

The exact member offset may change across game updates. The identification rule is:

  1. allow_func_addr writes one byte to this + <member_offset> (setter pattern)
  2. isallowed_func_addr is the next vtable entry (allow_vfunc_index + 1)
  3. The candidate reads and returns one unsigned byte from the same this + <member_offset>

If both conditions hold, the candidates are CNetworkMessages_AllowAdditionalMessageRegistration and CNetworkMessages_IsAdditionalMessageRegistrationAllowed.

5. Generate Function Signatures

ALWAYS Use SKILL /generate-signature-for-function with addr=<allow_func_addr> to generate a robust and unique func_sig for CNetworkMessages_AllowAdditionalMessageRegistration.

ALWAYS Use SKILL /generate-signature-for-function with addr=<isallowed_func_addr> to generate a robust and unique func_sig for CNetworkMessages_IsAdditionalMessageRegistrationAllowed.

Use the returned validated func_sig values in the next steps.

6. Write IDA Analysis Output as YAML for AllowAdditionalMessageRegistration

ALWAYS Use SKILL /write-vfunc-as-yaml to write the analysis results.

Required parameters:

  • func_name: CNetworkMessages_AllowAdditionalMessageRegistration
  • func_addr: <allow_func_addr>
  • func_sig: The validated signature from step 5
  • vfunc_sig: None

VTable parameters:

  • vtable_name: CNetworkMessages
  • vfunc_offset: <allow_vfunc_offset> in hex
  • vfunc_index: <allow_vfunc_index>

7. Write IDA Analysis Output as YAML for IsAdditionalMessageRegistrationAllowed

ALWAYS Use SKILL /write-vfunc-as-yaml to write the analysis results.

Required parameters:

  • func_name: CNetworkMessages_IsAdditionalMessageRegistrationAllowed
  • func_addr: <isallowed_func_addr>
  • func_sig: The validated signature from step 5
  • vfunc_sig: None

VTable parameters:

  • vtable_name: CNetworkMessages
  • vfunc_offset: <isallowed_vfunc_offset> in hex
  • vfunc_index: <isallowed_vfunc_index>

Function Characteristics

CNetworkMessages_AllowAdditionalMessageRegistration

  • Purpose: Sets whether additional network message registration is allowed on the CNetworkMessages instance
  • Binary: networksystem.dll / libnetworksystem.so
  • Parameters: (this, bool bAllow)
  • Return value: void

CNetworkMessages_IsAdditionalMessageRegistrationAllowed

  • Purpose: Returns whether additional network message registration is currently allowed
  • Binary: networksystem.dll / libnetworksystem.so
  • Parameters: (this) only
  • Return value: An unsigned byte / boolean flag loaded from the same member written by CNetworkMessages_AllowAdditionalMessageRegistration

Discovery Strategy

  1. Reuse the existing CNetworkMessages_RegisterNetworkFieldChangeCallbackInternal YAML to obtain the authoritative slot index
  2. Reuse the existing CNetworkMessages_vtable YAML to resolve the two adjacent vtable entries
  3. Confirm the semantic pair:
    • setter writes this + <member_offset>
    • adjacent getter returns this + <member_offset>
  4. Generate stable func_sig values from the resolved function bodies

This is robust because:

  • The vtable adjacency (RegisterNetworkFieldChangeCallbackInternal followed by AllowAdditionalMessageRegistration then IsAdditionalMessageRegistrationAllowed) is stable and explicit
  • The setter/getter pair must touch the same byte member
  • The final YAMLs store both the resolved function signatures and the precise vtable metadata

Output YAML Format

The output YAML filenames depend on the platform:

  • networksystem.dll -> CNetworkMessages_AllowAdditionalMessageRegistration.windows.yaml, CNetworkMessages_IsAdditionalMessageRegistrationAllowed.windows.yaml
  • libnetworksystem.so -> CNetworkMessages_AllowAdditionalMessageRegistration.linux.yaml, CNetworkMessages_IsAdditionalMessageRegistrationAllowed.linux.yaml

Arquivos desta versão

Permissões

PermissãoDeclaradaEncontrada na varredura
Lê arquivosNãoNão
Grava arquivosSimSim
Roda comandos no shellNãoNão
Usa a redeNãoNão
Usa conectoresSimSim
Controla um navegadorNãoNão

Achados da varredura

Revisado em 13 de nov. de 2026

A varredura não encontrou nada para apontar nesta versão.

Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.

VersãoPublicada emCommitSHA-256AssinaturaMudança de permissão
v2026.11.13-dcf202013 de nov. de 2026dcf20208c3f30d8Assinada–

Pergunte tudo o que o seu escopo permite.

Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.

  1. 1/3

    Crie a conta

    Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.

    Pessoa físicaEmpresa
  2. 2/3

    Adicione créditos

    No cartão. Você paga por token, sem assinatura.

    $5.00recarga mínima
  3. 3/3

    Pergunte

    No chat, ou instale o CLI e rode notholy login no terminal.

    $ notholy login