Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

wechat6.5? #42

Open
pxss opened this issue Apr 12, 2017 · 14 comments

Comments

@pxss
Copy link

commented Apr 12, 2017

wechat6.5 how to decrypt ?

@rom1504

This comment has been minimized.

Copy link

commented Apr 12, 2017

still the same

@ppwwyyxx

This comment has been minimized.

Copy link
Owner

commented Apr 28, 2017

@ChiChou Thanks very much for the details!! I'll try your method and update the code.

@ChiChou

This comment has been minimized.

Copy link

commented Apr 29, 2017

@ppwwyyxx Damn I was fooled. WeChat 6.5 uses the same password generator.

ced409b5-762a-4b5b-b397-3809604d1937

Sorry for misleading.

@ppwwyyxx

This comment has been minimized.

Copy link
Owner

commented Apr 29, 2017

So I only need to change the device id (previously IMEI number), right?

@ChiChou

This comment has been minimized.

Copy link

commented May 23, 2017

This may work:
https://gist.github.com/ChiChou/36556fd412a9e3216abecf06e084e4d9

It invokes JNI to unserialize the MicroMsg/CompatibleInfo.cfg file, which stores the actual device id (IMEI or whatever it generates).

@ppwwyyxx ppwwyyxx added the bug label Jun 16, 2017

@ppwwyyxx

This comment has been minimized.

Copy link
Owner

commented Nov 29, 2017

Decryption works for me after I tried other methods to get IMEI.

@tony-zdl

This comment has been minimized.

Copy link

commented Jan 18, 2018

@ppwwyyxx which method did you try to get IMEI?

@ppwwyyxx

This comment has been minimized.

Copy link
Owner

commented Jan 18, 2018

In the README.

@8enet

This comment has been minimized.

Copy link

commented Feb 6, 2018

@ChiChou Thanks, it work fine for me!
get the IMEI unexpectedly is 1234567890ABCDEF. 😂

@cs-usst

This comment has been minimized.

Copy link

commented Feb 17, 2018

@8enet How does that file work? I don't understand.

@ChiChou

This comment has been minimized.

Copy link

commented Feb 23, 2018

@cs-usst

The device id that WeChat uses does not always match IMEI. But WeChat will always store this id in file /data/data/com.tencent.mm/MicroMsg/CompatibleInfo.cfg, which contains a HashMap<Integer, Object> serialized with ObjectOutputStream. I wrote the gist with C to call Java runtime (void device_id(char *id, size_t len)).

Anyways, Java serialized string still looks as is, so simply pull this file from device and strings CompatibleInfo.cfg to pick it.

@ChiChou

This comment has been minimized.

Copy link

commented Feb 23, 2018

Tried deserialize that with python, but the javaobj from pypi looks buggy

@QiangF

This comment has been minimized.

Copy link

commented Apr 26, 2018

I get :

q@debian wechat-dump$ strings CompatibleInfo.cfg
java.util.HashMap
loadFactorI
    thresholdxp?@
java.lang.Integer
valuexr
java.lang.Number
java.lang.Boolean
valuexp
ZUKZUK Z1: swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt: ARMv7 Processor rev 1 (v7l): 7: Qualcomm MSM8974PRO-AC: 0000000000000000sq
AXKXESIIOBTUPLVJsq
867695023349383x

use the imei as 867695023349383x
still not working!

@prusswan

This comment has been minimized.

Copy link

commented Aug 23, 2018

@QiangF assuming your dump is correct, the IMEI should be AXKXESIIOBTUPLVJ (the sq bit is an artifact from improper deserialization - a proper way to do it can be found here: https://blog.csdn.net/jiezhi2013/article/details/22181771)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
9 participants
You can’t perform that action at this time.