Users have the freedom to rename files (tag them) before they
consider uploading. The 7878e6b.msi could result from the unpacking
of an EXE, if there were an EXE wrapper for the .msi file.
In some cases, you can see a nice tight clustering of names
and naming convention, which tells you you're on the right page.
For example, if you feed
"Carbon Helium Backup PC Setup.msi"
into Google, you might find a thread somewhere which
corroborates the file is legitimate. A private thread discussion
where someone listed the checksum, say.
I've sometimes used checksums from MDL, to judge whether various
installer ISOs for Windows are legit or not (back when it was hard
to find a Windows 7 installer, for OEM computer users). Originally,
the MSDN subscription ISOs had SHA1 and MD5 sums, then Microsoft
removed access to the checksum information, forcing people like me
to fish in MDL waters to get validation.
So the idea is to prove to your own satisfaction, that you've traced
the file backwards to the original author or source. This is necessary
in cases where the original site shutdown, and
archive.org doesn't
have it.
*******
Download jsMSIx (67 KB)
https://www.jsware.net/jsware/zips/jsmsix19.zip
SHA-256: 08112aff0c9d0d7a72e06cffec843b207ef5dc652b4eef62f1c5d0dd13341659
On extraction, you get this file, plus a Readme file
Name: jsMSIx.exe
Size: 196608 bytes (192 KiB)
SHA256: CC46F2227B8E284A9C3914A91492934B7B2F5A922424A3ABEC7C1087723F6A0A
Start the program and tell it where to find CarbonSetup.msi,
It will unpack the MSI. I try to put all the stuff in a work
folder, so it doesn't end up all over the place. Don't do this
work right in your Downloads folder, or you'll never find the
bits and pieces it saved out. Make a Downloads\WORK and drop
the bits and pieces in there.
You can see the usual bullshit detections :-/
https://www.virustotal.com/gui/file/cc46f2227b8e284a9c3914a91492934b7b2f5a922424a3abec7c1087723f6a0a
You'll find there is some sort of USB driver, something
related to ADB bus. And the BouncyCastle.Crypto? Not a clue :-)
There's also a signtool.exe in the kit.
You can get some idea what it might be for, but it's
a bit thin on details. You won't be able to right click the
INF and install the drivers, if for any reason they're not
signed for usage on a 64 bit OS. Anyway, that's plenty to
give you something to play with and work on.
I don't own a smartphone, so cannot test this. Having an
adb.exe on my machine is a waste of electrons :-)
Paul