Predator and CL could not provide any possible suspects.
Using Code Search for the file, "thunks.cc" assigning to the concern owner who might be related.

Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/349df72b01325e75fbcc25db9ee4766b13fdc433

@rockot -- Could you please look into the issue, kindly re-assign if this is not related to your changes.

Thanks!!

This is clearly use of Mojo before Mojo has been  initialized, not the result of the change linked in c#1. Looks like maybe FuzzerDriver is doing work too early.

I don't know who should own this but probably someone who works on the fuzzer. +tjbecker for a start.

Ah looks like the same bug as 755854.

ClusterFuzz has detected this issue as fixed in range 498116:498178.

Detailed report: https://clusterfuzz.com/testcase?key=6665262098284544

Fuzzer: libFuzzer_webcrypto_rsa_import_key_spki_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: ASSERT
Crash Address: 
Crash State:
  g_thunks.CreateMessagePipe
  MojoCreateMessagePipe
  mojo::CreateMessagePipe
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=495056:495085
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=498116:498178

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6665262098284544

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.