MacOS微信逆向分析-Frida-Toy模板网

这篇具有很好参考价值的文章主要介绍了MacOS微信逆向分析-Frida。希望对大家有所帮助。如果存在错误或未考虑完全的地方，请大家不吝赐教，您也可以点击"举报违法"按钮提交疑问。

PC下的微信二次开发相信大家都会了，那么本篇文章将带领大家使用Frida框架对Mac下微信来进行二次开发！

PS：还有一种静态注入的方式也不错，但是考虑到大家xcode安装包太大就不在这里展开啦。

PS：frida如何去使用大家得自己去学，本文不过多展开。

主要功能涉及如下：

微信消息发送
微信消息监听

1.微信版本

frida mac,ipad,macos,ipad,微信,云计算,大数据

预先善其事，必先利其器！请先准备如下分析工具

Hopper Disassembler
Class-dump
Frida
Pycharm(可选)
Vscode（可选）

3.Dump 出头文件

首先利用Class-Dump拿到微信的头文件，打开终端执行：

1	`class-dump` `-H` `/Applications/WeChat.app`

成功执行之后会生成很多的头文件了,如下所示

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

-rw-r--r--  1 n staff   927B  2 15 19:19 WXCPbQcwxtalkPackage.h

-rw-r--r--  1 n staff   975B  2 15 19:19 WXCPbReportItem.h

-rw-r--r--  1 n staff   1.7K  2 15 19:19 WXCPbSCAddVoiceGroupMemberResp.h

-rw-r--r--  1 n staff   772B  2 15 19:19 WXCPbSCCancelCreateVoiceGroupResp.h

-rw-r--r--  1 n staff   7.2K  2 15 19:19 WXCPbSCCreateVoiceGroupResp.h

-rw-r--r--  1 n staff   6.9K  2 15 19:19 WXCPbSCEnterVoiceRoomResp.h

-rw-r--r--  1 n staff   1.1K  2 15 19:19 WXCPbSCExitVoiceRoomResp.h

-rw-r--r--  1 n staff   1.2K  2 15 19:19 WXCPbSCModifyVoiceGroupInfoResp.h

-rw-r--r--  1 n staff   872B  2 15 19:19 WXCPbSCSubscribeLargeVideoResp.h

-rw-r--r--  1 n staff   867B  2 15 19:19 WXCPbSCSubscribeVideoResp.h

-rw-r--r--  1 n staff   2.0K  2 15 19:19 WXCPbSCVoiceClientSceneReportResp.h

-rw-r--r--  1 n staff   864B  2 15 19:19 WXCPbSCVoiceGetGroupInfoBatchResp.h

-rw-r--r--  1 n staff   637B  2 15 19:19 WXCPbSCVoiceMemberWhisperResp.h

-rw-r--r--  1 n staff   5.9K  2 15 19:19 WXCPbSCVoiceRedirectResp.h

-rw-r--r--  1 n staff   1.1K  2 15 19:19 WXCPbSCVoiceRoomHelloResp.h

-rw-r--r--  1 n staff   904B  2 15 19:19 WXCPbSKBuiltinBuffer_t.h

-rw-r--r--  1 n staff   686B  2 15 19:19 WXCPbSubscribeVideoMember.h

-rw-r--r--  1 n staff   2.7K  2 15 19:19 WXCPbSwitchVideoGroupResp.h

-rw-r--r--  1 n staff   1.4K  2 15 19:19 WXCPbVideoGroupMember.h

-rw-r--r--  1 n staff   671B  2 15 19:19 WXCPbVoiceClientScene.h

-rw-r--r--  1 n staff   1.2K  2 15 19:19 WXCPbVoiceClientSceneExt.h

-rw-r--r--  1 n staff   2.9K  2 15 19:19 WXCPbVoiceConf.h

首先那么多的文件我们肯定不能一个个的去看，那样效率太低。相信大家做开发为了自己好维护代码，肯定不会给对象随便命名为abc这种吧！不会吧！不会吧！真的有这种人啊！！！但是我相信腾讯的程序员肯定不会这么做！！微信核心的功能是啥？是发消息哦，那么消息的英文是啥？Message ！对就是他。所以我们就先塞选下这个Message！

# n @ localhost in ~/vscodewsp/wechat/dump [20:58:22]
$ ll |wc -l
    4922
 
# n @ localhost in ~/vscodewsp/wechat/dump [20:58:29]
$ ll -l |grep Message|wc -l
     157
 
# n @ localhost in ~/vscodewsp/wechat/dump [20:58:42]

执行如上命令我们把文件数从4922个转变到157了。这样就缩小了范围啦！如何再次缩小范围尼！那么就得是看大家的开发习惯啦，我一般做业务我都喜欢写service，controller，这种业务类名，于是我再次....

# n @ localhost in ~/vscodewsp/wechat/dump [20:58:42]

$ ll -l |grep Message|grep Service|wc -l

9

# n @ localhost in ~/vscodewsp/wechat/dump [21:02:13]

$ ll -l |grep Message|grep Service

-rw-r--r-- 1 n staff 5.1K 2 15 19:19 FTSFileMessageService.h

-rw-r--r-- 1 n staff 382B 2 15 19:19 IMessageServiceAppExt-Protocol.h

-rw-r--r-- 1 n staff 980B 2 15 19:19 IMessageServiceFileExt-Protocol.h

-rw-r--r-- 1 n staff 381B 2 15 19:19 IMessageServiceFileReTransferExt-Protocol.h

-rw-r--r-- 1 n staff 755B 2 15 19:19 IMessageServiceImageExt-Protocol.h

-rw-r--r-- 1 n staff 780B 2 15 19:19 IMessageServiceVideoExt-Protocol.h

-rw-r--r-- 1 n staff 407B 2 15 19:19 IMessageServiceVideoReTransferExt-Protocol.h

-rw-r--r-- 1 n staff 3.1K 2 15 19:19 MMFTSMessageService.h

-rw-r--r-- 1 n staff 20K 2 15 19:19 MessageService.h

# n @ localhost in ~/vscodewsp/wechat/dump [21:02:25]

$

哎呦哎呦，就剩9个文件啦？？？那么这个一个个看也不碍事！！有时间就是任性！！！哼。最终定位到MessageService.h 打开一看，果然尼！真是运气好！

- (id)SendLocationMsgFromUser:(id)arg1 toUser:(id)arg2 withLatitude:(double)arg3 longitude:(double)arg4 poiName:(id)arg5 label:(id)arg6;

- (id)SendNamecardMsgFromUser:(id)arg1 toUser:(id)arg2 containingContact:(id)arg3;

- (id)SendStickerStoreEmoticonMsgFromUsr:(id)arg1 toUsrName:(id)arg2 md5:(id)arg3 productID:(id)arg4;

- (id)SendEmoticonMsgFromUsr:(id)arg1 toUsrName:(id)arg2 md5:(id)arg3 emoticonType:(unsigned int)arg4;

- (id)SendImgMessage:(id)arg1 toUsrName:(id)arg2 thumbImgData:(id)arg3 midImgData:(id)arg4 imgData:(id)arg5 imgInfo:(id)arg6;

- (id)SendTextMessage:(id)arg1 toUsrName:(id)arg2 msgText:(id)arg3 atUserList:(id)arg4;

- (id)SendAppMusicMessageFromUser:(id)arg1 toUsrName:(id)arg2 withTitle:(id)arg3 url:(id)arg4 description:(id)arg5 thumbnailData:(id)arg6;

- (id)SendAppURLMessageFromUser:(id)arg1 toUsrName:(id)arg2 withTitle:(id)arg3 url:(id)arg4 description:(id)arg5 thumbnailData:(id)arg6;

- (id)SendAppURLMessageFromUser:(id)arg1 toUsrName:(id)arg2 withTitle:(id)arg3 url:(id)arg4 description:(id)arg5 thumbUrl:(id)arg6 sourceUserName:(id)arg7 sourceDisplayName:(id)arg8;

你看这功能不就来了嘛？Send开头的都是发送消息的函数啊。OK完事。那么就开始搞它！

PS：其实分析时候还是挺费事的，但是大家自己多动手肯定能找到的！

5.FridaHook验证

为了验证自己的分析是不是正确的，我们得进行验证啊，怎么验证？frida大法好！执行以下命令：

frida-trace -m "-[MessageService Send*]" 微信

$ frida-trace -m "-[MessageService Send*]" 微信

Instrumenting...

-[MessageService SendTextMessageWithString:toUser:]: Auto-generated handler at "/Users/n/vscodewsp/wechat/__handlers__/MessageService/SendTextMessageWithString_toUser_.js"

-[MessageService SendAppURLMessageFromUser:toUsrName:withTitle:url:description:thumbUrl:sourceUserName:sourceDisplayName:]: Auto-generated handler at "/Users/n/vscodewsp/wechat/__handlers__/MessageService/SendAppURLMessageFromUser_toUsrN_eaefd0af.js"

------------------------------------------------------------------------------

-[MessageService SendNamecardMsgFromUser:toUser:containingContact:]: Auto-generated handler at "/Users/n/vscodewsp/wechat/__handlers__/MessageService/SendNamecardMsgFromUser_toUser_c_b5899e8d.js"

Started tracing 18 functions. Press Ctrl+C to stop.

然后会在当前目录生成handlers文件夹，里面是frida为我们自动生成的hook脚本文件。我们使用微信发送一条消息试试。

然后终端会输出一条信息：

195323 ms -[MessageService SendTextMessage:0x600000b6fae0 toUsrName:0x6503cfa934d442eb msgText:0x6000002ec860 atUserList:0x600000a73570]

这个就是触发了发送消息的hook信息啦。SendTextMessage 是不是跟我们在头文件信息里面看到的一样。

我们找到handles文件夹下SendTextMessage这个js文件，试试修改log输出然后再执行

frida-trace -m "-[MessageService Send*]" 微信

我们可以看到输出变啦
2908 ms -[我的消息测试 SendTextMessage:0x600000b6fae0 toUsrName:0x6503cfa934d442eb msgText:0x6722df8306c2767b atUserList:0x6000009c2760]

如此可以确定我们找到的函数就是发送消息的函数。那么看看能不能打印出自己发送的消息内容

- (id)SendTextMessage:(id)arg1 toUsrName:(id)arg2 msgText:(id)arg3 atUserList:(id)arg4;

可以看到这个函数一共有4个参数：参数一：暂时不知道。参数二：toUsrName，我们可以知道是消息发送给谁的。参数三：msgText 消息内容，消息四：暂时不知道

分别把这四个参数给打印出来试试！修改js文件

onEnter(log, args, state) {

console.log(`-[我的消息测试 SendTextMessage:${args[2]} toUsrName:${args[3]} msgText:${args[4]} atUserList:${args[5]}]`);

console.log("arg[1] -> " + new ObjC.Object(args[2]))

console.log("arg[2] -> " + new ObjC.Object(args[3]))

console.log("arg[3] -> " + new ObjC.Object(args[4]))

console.log("arg[4] -> " + new ObjC.Object(args[5]))

},

然后执行 frida-trace -m "-[MessageService Send*]" 微信 发送一条消息

frida mac,ipad,macos,ipad,微信,云计算,大数据

arg[1] -> wxid_*****63i822

arg[2] -> filehelper

arg[3] -> 这个是消息测试

arg[4] ->

/* TID 0x307 */

14534 ms -[我的消息测试 SendTextMessage:0x600000b6fae0 toUsrName:0x6503cfa934d442eb msgText:0x600000adefd0 atUserList:0x600000add470]

我们可以看到终端正确响应了，输出的正是我们发送的消息。那么我修改发送内容试试？？添加如下代码：

args[4] = ObjC.classes.NSString.stringWithString_("MacOS微信分析")

然后微信发送任何消息，对方都将收到的是MacOS微信分析

frida mac,ipad,macos,ipad,微信,云计算,大数据

这样我们就确定了发送文本消息的函数就是这个。那么我们如何主动调用它呢？

6.Hopper分析程序代码

从上面的分析我们看到发送消息需要四个参数。第一个：通过分析应该是我们自己的微信id，第二个：对方的微信id，第三个：消息内容，第四个：可以为null

那么就打开hopper拖入微信具体分析分析吧

应用程序->微信->显示包内容->Contents->MacOS->WeChat 拖进hopper然后默认选项即可

frida mac,ipad,macos,ipad,微信,云计算,大数据

在左边输入SendTextMessage搜索我们可以看到上面四个应该是我们所需要的，都打开看下伪代码。（我们分析需要找到函数调用的地方就能知道传参，然后再去分析参数是如何而来。那么除了函数定义地方代码，其余的都可以找到。

MMMessageSendLogic ：

/* @class MMMessageSendLogic */

-(unsigned char)sendTextMessageWithString:(void *)arg2 mentionedUsers:(void *)arg3 {

r14 = self;

r15 = [arg2 retain];

r12 = [arg3 retain];

r13 = [[CUtility filterStringForTextMessage:r15] retain];

[r15 release];

if ([r13 length] != 0x0) {

stack[-64] = r12;

rax = [r13 lengthOfBytesUsingEncoding:0x4];

rbx = rax;

if (rax >= 0x4001) {

rax = [[NSString alloc] initWithFormat:@"ERROR: Text too long, length: %lu, utf8 length: %lu", [r13 length], rbx];

stack[0] = "-[MMMessageSendLogic sendTextMessageWithString:mentionedUsers:]";

[MMLogger logWithMMLogLevel:0x2 module:"ComposeInputView" file:0x103e0e162 line:0x112 func:stack[0] message:rax];

[rax release];

rax = [NSBundle mainBundle];

rax = [rax retain];

stack[-72] = rax;

r15 = [[rax localizedStringForKey:@"Message.Input.Too.Long.Title" value:@"" table:0x0] retain];

rax = [NSBundle mainBundle];

rax = [rax retain];

r14 = rax;

rax = [rax localizedStringForKey:@"Message.Input.Too.Long.Content" value:@"" table:0x0];

rax = [rax retain];

[NSAlert showAlertSheetWithTitle:r15 message:rax completion:0x0];

[rax release];

[r14 release];

[r15 release];

[stack[-72] release];

r14 = 0x0;

r12 = stack[-64];

}

else {

rax = [WeChat sharedInstance];

rax = [rax retain];

r15 = [[rax CurrentUserName] retain];

[rax release];

rax = [r14 currnetChatContact];

rax = [rax retain];

r14 = [[rax m_nsUsrName] retain];

[rax release];

r12 = [[MMServiceCenter defaultCenter] retain];

objc_unsafeClaimAutoreleasedReturnValue([[[r12 getService:[MessageService class]] retain] SendTextMessage:r15 toUsrName:r14 msgText:r13 atUserList:stack[-64]]);

[rax release];

[r12 release];

[r14 release];

[r15 release];

r14 = 0x1;

r12 = stack[-64];

r13 = r13;

}

else {

rax = [[NSString alloc] initWithFormat:@"ERROR: Text is empty, can't send"];

stack[0] = "-[MMMessageSendLogic sendTextMessageWithString:mentionedUsers:]";

[MMLogger logWithMMLogLevel:0x2 module:"ComposeInputView" file:0x103e0e162 line:0x10c func:stack[0] message:rax];

[rax release];

r14 = 0x0;

}

[r13 release];

[r12 release];

rax = r14 & 0xff;

return rax;

}

这个伪代码看的就比较清楚了，

objc_unsafeClaimAutoreleasedReturnValue([[[r12 getService:[MessageService class]] retain] SendTextMessage:r15 toUsrName:r14 msgText:r13 atUserList:stack[-64]]);

我们可以看到第一个参数是r15，网上追溯r15，

r15 = [[rax CurrentUserName] retain]; r15是这里赋值的，那么再看看CurrentUserName方法内容。

-(void *)CurrentUserName {

if ([self isLoggedIn] != 0x0) {

rdi = [[CUtility GetCurrentUserName] retain];

}

else {

rdi = 0x0;

}

rax = [rdi autorelease];

return rax;

}

可以看到是先判断是不是已经登录，然后调用CUtility类里面的GetCurrentUserName方法获得的。那么第一个参数我们就知道了。其余三个参数我们也很容易的可以手动构造。我们编写js脚本代码

7.编写frida脚本

console.log("init success");

function SendTextMessage(wxid, msg) {

var message = ObjC.chooseSync(ObjC.classes.MessageService)[0]

var username = ObjC.classes.CUtility.GetCurrentUserName();

console.log(username)

console.log("Type of arg[0] -> " + message)

var toUsrName = ObjC.classes.NSString.stringWithString_(wxid);

var msgText = ObjC.classes.NSString.stringWithString_(msg);

message["- SendTextMessage:toUsrName:msgText:atUserList:"](username, toUsrName, msgText, null);

}

SendTextMessage("filehelper","主动调用发送信息！")

将以上文本保存js文件，然后执行以下命令：

frida 微信 --debug --runtime=v8 --no-pause -l test.js

我们就可以看到微信上发送了一条消息

frida mac,ipad,macos,ipad,微信,云计算,大数据

8.消息监听

上面我们实现了微信消息的篡改及主动发送功能。那么我们再去看看微信是如何接到消息信息的！每当有人活或者群给我们发送消息的时候电脑或手机上一般都会提示通知，那么通知的英文是什么？notify 翻译就是通知的意思，我们碰碰运气看看能不能找到相关字样。还是在MessageService里面我们找到了- (void)notifyAddMsgOnMainThread:(id)arg1 msgData:(id)arg2; 这个方法，如何去确定它到底是不是尼？还是继续用frida去进行验证。

1	`frida-trace` `-m` `"-[MessageService notify*]"` `微信`

$ frida-trace -m "-[MessageService notify*]" 微信
Instrumenting...                                                       
-[MessageService notifyModMsgOnMainThread:msgData:]: Loaded handler at "/Users/n/vscodewsp/wechat/__handlers__/MessageService/notifyModMsgOnMainThread_msgData_.js"
-[MessageService notifyAppMsgUploadProgress:msgData:uploadedBytes:totalBytes:]: Loaded handler at "/Users/n/vscodewsp/wechat/__handlers__/MessageService/notifyAppMsgUploadProgress_msgDa_9b03499e.js"
-[MessageService notifyVideoMsgUploadProgress:msgData:uploadedBytes:totalBytes:]: Loaded handler at "/Users/n/vscodewsp/wechat/__handlers__/MessageService/notifyVideoMsgUploadProgress_msg_e1db5f92.js"
-[MessageService notifyNewMsgNotificationOnMainThread:msgData:]: Loaded handler at "/Users/n/vscodewsp/wechat/__handlers__/MessageService/notifyNewMsgNotificationOnMainTh_d56d83b5.js"
-[MessageService notifyChatSyncMsgsOnMainThread:msgList:]: Loaded handler at "/Users/n/vscodewsp/wechat/__handlers__/MessageService/notifyChatSyncMsgsOnMainThread_msgList_.js"
-[MessageService notifyChatSyncMessagesMergedOnMainThread:]: Loaded handler at "/Users/n/vscodewsp/wechat/__handlers__/MessageService/notifyChatSyncMessagesMergedOnMainThread_.js"
-[MessageService notifyRevokePatMsgOnMainThread:n64MsgId:]: Loaded handler at "/Users/n/vscodewsp/wechat/__handlers__/MessageService/notifyRevokePatMsgOnMainThread_n64MsgId_.js"
-[MessageService notifyAddRevokePromptMsgOnMainThread:msgData:]: Loaded handler at "/Users/n/vscodewsp/wechat/__handlers__/MessageService/notifyAddRevokePromptMsgOnMainTh_81637ebf.js"
-[MessageService notifyDelMsgOnMainThread:msgData:isRevoke:]: Loaded handler at "/Users/n/vscodewsp/wechat/__handlers__/MessageService/notifyDelMsgOnMainThread_msgData_5bbc2297.js"
-[MessageService notifyMsgDeletedForSessionOnMainThread:]: Loaded handler at "/Users/n/vscodewsp/wechat/__handlers__/MessageService/notifyMsgDeletedForSessionOnMainThread_.js"
-[MessageService notifyDelAllMsgOnMainThread:]: Loaded handler at "/Users/n/vscodewsp/wechat/__handlers__/MessageService/notifyDelAllMsgOnMainThread_.js"
-[MessageService notifyAddMsgListForSessionOnMainThread:]: Loaded handler at "/Users/n/vscodewsp/wechat/__handlers__/MessageService/notifyAddMsgListForSessionOnMainThread_.js"
-[MessageService notifyUnreadCntChangeOnMainThread:]: Loaded handler at "/Users/n/vscodewsp/wechat/__handlers__/MessageService/notifyUnreadCntChangeOnMainThread_.js"
-[MessageService notifyMsgResendOnMainThread:msgData:]: Loaded handler at "/Users/n/vscodewsp/wechat/__handlers__/MessageService/notifyMsgResendOnMainThread_msgData_.js"
-[MessageService notifyImgMsgUploadProgress:msgData:uploadedBytes:totalBytes:]: Loaded handler at "/Users/n/vscodewsp/wechat/__handlers__/MessageService/notifyImgMsgUploadProgress_msgDa_e4e0cd43.js"
-[MessageService notifyAppMsgDownloadProgress:msgData:downloadedBytes:totalBytes:]: Loaded handler at "/Users/n/vscodewsp/wechat/__handlers__/MessageService/notifyAppMsgDownloadProgress_msg_4e191704.js"
-[MessageService notifyUIAndSessionOnMainThread:withMsg:]: Loaded handler at "/Users/n/vscodewsp/wechat/__handlers__/MessageService/notifyUIAndSessionOnMainThread_withMsg_.js"
-[MessageService notifyAddMsgOnMainThread:msgData:]: Loaded handler at "/Users/n/vscodewsp/wechat/__handlers__/MessageService/notifyAddMsgOnMainThread_msgData_.js"
Started tracing 18 functions. Press Ctrl+C to stop.

我们可以看到有不少的方法被hook了，但是没事。我们用微信发送一个消息给自己或者其他人都可以看看输出。

/* TID 0x307 */

157082 ms -[MessageService notifyAddMsgOnMainThread:0x6503cfa934d442eb msgData:0x7fd903c9fa00]

/* TID 0x31e17 */

157092 ms -[MessageService notifyUnreadCntChangeOnMainThread:0x6503cfa934d442eb]

/* TID 0xb5c27 */

157228 ms -[MessageService notifyModMsgOnMainThread:0x6503cfa934d442eb msgData:0x7fd903c9fa00]

我们可以看到三层相关的调用，那么我们就先看第一个notifyAddMsgOnMainThread 修改下js文件。

onEnter(log, args, state) {

log(`-[MessageService notifyAddMsgOnMainThread:${args[2]} msgData:${args[3]}]`);

},

以我们上面的经验很快的就可以看出这个应该就是消息接受的方法，msgdata就是我们所需要的消息内容。那么我们还是得继续验证。把参数都打印出来看看。修改添加如下js

1 2	`console.log("Type of arg[2] -> "` `+` `new ObjC.Object(args[2]).$className)` `console.log("Type of arg[3] -> "` `+` `new ObjC.Object(args[3]).$className)`

这两句话是为了输出2个参数的类型。然后也修改下frida命令执行

1	`frida-trace` `-m` `"-[MessageService notifyAddMsgOnMainThread*]"` `微信`

可以看到第一个参数是String，第二个参数是MessageData

$ frida-trace -m "-[MessageService notifyAddMsgOnMainThread*]" 微信

Instrumenting...

-[MessageService notifyAddMsgOnMainThread:msgData:]: Loaded handler at "/Users/n/vscodewsp/wechat/__handlers__/MessageService/notifyAddMsgOnMainThread_msgData_.js"

Started tracing 1 function. Press Ctrl+C to stop.

Type of arg[2] -> NSTaggedPointerString

Type of arg[3] -> MessageData

/* TID 0x307 */

2170 ms -[MessageService notifyAddMsgOnMainThread:0x6503cfa934d442eb msgData:0x7fd90401c960]

MessageData是消息的结构体，那么我们就去头文件中搜索一下这个MessageData

# n @ localhost in ~/vscodewsp/wechat/dump [7:46:01] C:1

$ ll -l|grep MessageData

-rw-r--r-- 1 n staff 2.5K 2 15 19:19 FTSFileMessageData.h

-rw-r--r-- 1 n staff 2.0K 2 15 19:19 FTSMessageData.h

-rw-r--r-- 1 n staff 794B 2 15 19:19 IMessageDataExt-Protocol.h

-rw-r--r-- 1 n staff 6.2K 2 15 19:19 MMChatMessageDataSource.h

-rw-r--r-- 1 n staff 25K 2 15 19:19 MessageData.h

-rw-r--r-- 1 n staff 550B 2 15 19:19 MessageDataGroup.h

-rw-r--r-- 1 n staff 2.9K 2 15 19:19 MessageDataPackedInfo.h

-rw-r--r-- 1 n staff 262B 2 15 19:19 NSPasteboard-MessageData.h

可以看到是有MessageData这个文件的。那么我们打开看看

@interface MessageData : NSObject <NSPasteboardItemDataProvider, IAppMsgPathMgr, IMsgExtendOperation, NSCopying, WCTTableCoding, WCTColumnCoding>

{

unsigned int mesLocalID;

long long mesSvrID;

NSString *fromUsrName;

NSString *toUsrName;

unsigned int messageType;

NSString *msgContent;

NSString *msgVoiceText;

unsigned int m_uiVoiceToTextStatus;

unsigned int msgStatus;

unsigned int msgImgStatus;

NSString *msgRealChatUsr;

NSString *msgPushContent;

unsigned int m_uiTranslateStatus;

NSString *msgSource;

unsigned int mesDes;

unsigned int msgSeq;

BOOL bForward;

NSData *m_dtThumbnail;

unsigned int msgCreateTime;

unsigned int m_uiSendTime;

unsigned int m_uiDownloadStatus;

id <IMsgExtendOperation> m_extendInfoWithMsgType;

id <IMsgExtendOperation> m_extendInfoWithFromUsr;

BOOL isAutoIncrement;

BOOL m_bShouldShowAll;

BOOL m_bIsMultiForwardMessage;

BOOL m_shouldReloadOriginal;

BOOL m_bHasOriginalMessage;

unsigned int IntRes1;

unsigned int IntRes2;

unsigned int m_uiFileUploadStatus;

unsigned int m_uiOriginalImgHeight;

unsigned int m_uiOriginalImgWidth;

unsigned int m_uiSrcCreateTime;

unsigned int _m_nsMsgCrc32;

unsigned int _m_uiUploadedBytes;

unsigned int _m_uiDownloadedBytes;

unsigned int _m_uiTotalBytes;

int _m_nCdnServerRetCode;

unsigned int _m_uiResendMessageCount;

long long lastInsertedRowID;

NSString *StrRes1;

NSString *StrRes2;

MMTranslateResult *m_nsTranslationResult;

NSString *m_nsFilePath;

NSString *m_nsVideoPath;

NSString *m_nsVideoThumbPath;

NSString *dataMd5;

MessageData *m_refMessageData;

MessageDataPackedInfo *m_packedInfo;

NSString *m_nsSrcUserName;

NSString *m_nsSrcNickName;

NSString *m_nsAtUserList;

NSString *_m_nsImgFileName;

NSString *_m_nsBigFileErrMsg;

SecondMsgNode *_secondMsgNode;

MessageData *_referHostMsg;

}

看各个属性名应该没问题，就是他。那么我们直接修改js代码进行输出试试。

var MessageData = new ObjC.Object(args[3]).$ivars;

console.log("fromUsrName -> " + MessageData.fromUsrName)

console.log("toUsrName -> " + MessageData.toUsrName)

console.log("msgContent -> " + MessageData.msgContent)

运行frida-trace -m "-[MessageService notifyAddMsgOnMainThread*]" 微信

-[MessageService notifyAddMsgOnMainThread:msgData:]: Loaded handler at "/Users/n/vscodewsp/wechat/__handlers__/MessageService/notifyAddMsgOnMainThread_msgData_.js"

Started tracing 1 function. Press Ctrl+C to stop.

Type of arg[2] -> NSTaggedPointerString

Type of arg[3] -> MessageData

fromUsrName -> wxid_pk1reltk63i822

toUsrName -> filehelper

msgContent -> 消息监听测试

/* TID 0x307 */

14909 ms -[MessageService notifyAddMsgOnMainThread:0x6503cfa934d442eb msgData:0x7fd904426980]

如上我们可以看到成功接收到别人发送的消息内容。文章来源地址https://www.toymoban.com/news/detail-758620.html

到了这里，关于MacOS微信逆向分析-Frida的文章就介绍完了。如果您还想了解更多内容，请在右上角搜索TOY模板网以前的文章或继续浏览下面的相关文章，希望大家以后多多支持TOY模板网！