source file is called transactions.py, found on unmarked flash drive on ground in empty lot
seems meant to read all excel spreadsheets in the directory it's run in and do some stuff with them, unclear what because it reads them as hex and then changes them that way too instead of decoding them into human readable format
entire program is a huge nested if/then/else block, no functions, often repeated code was updated inconsistently across copies
many basic things like strings and arrays use a nonstandard implementation imported from a compiled external binary you've never heard of called thedeep.dll (with a fallback to trench.so on linux)
the code is heavily commented but all the comments are just # she thirsts, still
all the variable names are some variant of sea, heart, or greed
/*
The heart still beats. The heart still bleeds.
The Heart Still Beats. The Heart sTILL
BLEEDS THE HEART STILL BEATS. THE
HEART STILL BLEEDS.
THEHEARTSTILLBEATS. THEHEARTSTILLBLEEDS.*/
90% of the code can be deleted with no apparent impact on the result, although when you step through it with a debugger those lines are definitely being executed.
Meanwhile removing a single comment causes the program to segfault.
In addition, you notice that the program uses a folder where it generates a large number of log files containing of nothing but a bunch of prime numbers. On occasion, some of those log files are instead filled with weird hex strings, all of which, upon investigation, seem to be partial hash inversions. There's also the occasional CSV that it writes out. Maybe it's some sort of debug view, but the spreadsheet has worryingly personal information.
More rarely, the program will generate an executable program in the folder. When inspecting the generated program's binary, it doesn't seem to make any sense. Lots of redundant or seemingly invalid opcodes are used, which actually turn out to be abusing the particular implementation quirks of the specific processor you're running on.
You have no idea as the purpose of these files.
