c01-noreset-uin-stack.md 2.47 KB

c01.c: NoResetUinStack — Full Diagnosis (2026-07-25)

Evidence Timeline

WeChat 8.0.74 on Pixel 10 Fold (Android 16), wechathook v1 with device spoof SM-X700.

12:53:29  — Sub-processes start (appbrand0/1, xweb), no main process
13:15:28  — Main process pid=1702 starts, all hooks injected:
            hookDeviceSpoof: → Samsung SM-X700 tablet
            pad-spoof flag ON
            BroadcastReceivers registered in com.tencent.mm
            bk.A() called -> TRUE
13:53:19  — send_image_via_hook('yibooo', 'daily_digest_1tgo.png') called
            → SEND_IMAGE_INTERNAL received by hook
            → sendImageViaAPI: built o70.k+o70.h, plugin=b80.u
            → hookImageSend: captured b80.u@43a9d3d
            → FAILED: c01.c: NoResetUinStack
13:53:53  — LoginPasswordUI.onCreate() -> N VISIBLE + m4 attached
            (user kicked back to login screen)
13:53:53  — bk.A() still returns TRUE (spoof still working)

Key observation: 38 minutes of normal logged-in operation between hook injection and the first send attempt. Hook injection itself did NOT trigger detection.

What c01.c Does

c01.c is WeChat's internal session integrity validator for the message pipeline. It checks that a message being composed has a valid "Reset UIN Stack" — a chain of UI/session state that proves the message originated from a legitimate user interaction.

The hook's sendViaAPI bypasses the normal UI → message factory → UIN stack chain, directly constructing and injecting message objects. c01.c detects the missing UIN stack and:

  1. Blocks the message (NoResetUinStack)
  2. Invalidates the current session (security measure)
  3. WeChat redirects to LoginPasswordUI

Distinguishing from Plugin.Zero

The log entry at com.tencent.mm.plugin.zero.a.b(SourceFile:7) appeared in the same stack trace but is NOT the detection mechanism. It's part of WeChat's normal image upload pipeline. The actual trigger is c01.c.

Affected Hook Methods

Any hook that sends messages via WeChat's internal API without proper UIN stack simulation:

  • sendImageViaAPI (b80.u) → confirmed trigger
  • sendTextViaAPI (w11.s1) → likely same trigger
  • sendVoiceViaAPI (modelbase.l.a) → likely same trigger

Fix Direction

The wechathook source on Mac needs to either:

  1. Simulate the UIN stack initialization before calling the message factory, OR
  2. Hook c01.c itself to bypass the check, OR
  3. Find an alternative message injection path that doesn't go through c01.c