xiaohongshu-reconnaissance.md 4.35 KB

小红书 (Xiaohongshu) Reconnaissance

Last verified: 2026-06-27, app version unknown (recent from Google Play)

Identity

  • Package: com.xingin.xhs
  • APK path: /data/app/~~JGzwvh-T95r5zJVopw-9zQ==/com.xingin.xhs-PG9393qyAVp5M0AZSFGWlA==/base.apk
  • APK size: 164MB (multi-dex, likely hardened)
  • UID: u0_a341

Local Storage Layout

/data/data/com.xingin.xhs/

.bistore/              — BiStore data
.tistore/              — TiStore data
app_ads_splash_btn_bg/ — Ad splash backgrounds
app_asserts/           — Runtime asserts
app_cache/             — App cache
app_jniLibs/           — Extracted .so libraries
app_js_engine_v8/      — V8 JS engine runtime
app_p_mark/            — Some mark data
app_pcdn_sdk_module/   — PCDN SDK (video/image CDN)
app_pcdn_sdk_module_jinshan/   — Jinshan PCDN
app_pcdn_sdk_module_kuaishou/  — Kuaishou PCDN
app_petal/             — 花瓣 (Huawei Petal) SDK
app_r1_webview_64/     — WebView runtime
app_tencent_lite_av/   — Tencent LiteAV (video calls/streaming)
app_textures/          — GPU textures
app_webview_com.xingin.xhs/ — WebView data
app_xy_robust/         — Robust hot-fix framework
app_xylog_v2/          — Custom logging v2
databases/             — ONLY SDK databases (see below)
files/
  mmkv/                — MMKV key-value store (tokens, config, login state)
  raw_swift_data/      — Cached PNG images only (not API data!)
  r_key_info           — Binary encryption key material
  defaultserver_key.pub — Server public key
  longlink_log/        — Long-lived connection logs
  mp3/                 — Audio cache
shared_prefs/          — Mostly SDK prefs (JPush, Bugly, LocationSDK)

Databases (SDK-only, no content DB)

Database Purpose
AdDB Ads
ads_download_db Ad downloads
advert_emitter.sqlite Ad event emitter
analysisemitter.sqlite Analytics event emitter
cg.db Unknown (SDK)
dim.db Unknown (SDK)
gtc3-key.db GTC/encryption key

Critical finding: There is NO main content database. No message table, no post/note table, no user profile table. This app is 100% server-driven — all content comes from API calls.

Shared Prefs (SDK-dominated)

Most prefs are from third-party SDKs:

  • cn.jiguang.* — JPush (notifications)
  • cn.jpush.* — JPush config
  • BuglySdkInfos.xml — Tencent Bugly (crash reporting)
  • WebViewChromiumPrefs.xml — WebView
  • StrategySP.xml — Some strategy config
  • azeroth.xml.xml — Possibly main app config
  • Push_Page_Config.xml — Push page routing

No obvious auth.xml or user_token.xml — auth tokens likely stored in MMKV.

MMKV Contents (potential token targets)

Key stores found:

  • AppClientPushStrategy — Push strategy config
  • GrowthIdentifyManager — Growth/analytics identification
  • IMRecentChatsManager — IM chat management
  • LoginDelay — Login delay tracking
  • MOCK_LOCATION — Mock location flag
  • OverSeaAppConfig — Overseas version config
  • XYSalvage — Salvage/repair framework
  • abtest_config — A/B test config
  • app_cold_start_record — Cold start timestamps

None obviously named "auth" or "token" but LoginDelay and XYSalvage are worth investigating with Frida for session tokens.

Key Observations

  1. Heavy SDK footprint — Alibaba PCDN, Tencent LiteAV, Bugly, JPush, V8 engine. APK bulk is from SDKs.
  2. Robust hot-fix (app_xy_robust) — App can push code changes without Play Store update. Decompiled code may be stale.
  3. No local content DB — Must use Frida to intercept API responses for data extraction.
  4. raw_swift_data is images only — Confirmed PNG headers. Not API response cache.
  5. r_key_info is binary — Not plaintext despite file reporting UTF-8. Likely encrypted key material.
  6. defaultserver_key.pub — Public key for API communication. Companion to r_key_info.

Given the server-driven architecture:

  1. Data extraction: Frida hook on OkHttp/Retrofit (or custom HTTP stack) to capture API response JSON
  2. Auth token: Hook MMKV decodeString or SharedPreferences getString during app launch
  3. Posting API: Capture the post-creation request through Frida, extract signature algorithm, replay with curl
  4. Static analysis fallback: If Frida hooks fail, decompile with jadx on desktop (164MB APK likely OOMs on phone)