this post was submitted on 19 Sep 2026
39 points (97.6% liked)

Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ

70572 readers
140 users here now

⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.

Rules • Full Version

1. Posts must be related to the discussion of digital piracy

2. Don't request invites, trade, sell, or self-promote

3. Don't request or link to specific pirated titles, including DMs

4. Don't submit low-quality posts, be entitled, or harass others

Loot, Pillage, & Plunder

We heartily recommend visiting the free port of freemediaheckyeah (aka FMHY) while you sail the high seas, for all the freshest links the ocean has to offer.

📜 c/Piracy Wiki (Community Edition):

🏴‍☠️ Other communities

FUCK ADOBE!

Torrenting/P2P:

Gaming:

💰 Please help cover server costs.

Ko-Fi Liberapay
Ko-fi Liberapay

founded 3 years ago
MODERATORS
db0@lemmy.dbzer0.com
Flatworm7591@lemmy.dbzer0.com
RandomLegend@lemmy.dbzer0.com
Andromxda@lemmy.dbzer0.com
CosmicTurtle0@lemmy.dbzer0.com
tenchiken@lemmy.dbzer0.com
unruffled@anarchist.nexus
39
How do you vet executables? (piefed.blahaj.zone)
submitted 2 days ago by akunohana@piefed.blahaj.zone to c/piracy@lemmy.dbzer0.com
37 comments fedilink hide all child comments
 

I have found some software on 1337 that a friend was asking for. It's for Windows and I'm on Linux. Is test running the software inside a VM the only way to securely vet it (to see what connections it tries to make and what processes it starts)? On VirusTotal, I get one positive and 66 negatives. Preferably, I'd like to hand over the software without worrying about giving them malicious code...

you are viewing a single comment's thread
view the rest of the comments
[–] frongt@lemmy.zip 3 points 2 days ago (1 children)

You can also put it through sandboxes like joesandbox or cuckoo to try to trigger and detect a payload. But some malware will expect this and not execute.

Ultimately, judge your own risk tolerance by how much you trust the source, how much you want the software, what kind of systems protection you have in place (antivirus, antimalware, permissions control, backups), and how much you can afford to have your system compromised.

[–] akunohana@piefed.blahaj.zone 1 points 1 day ago

Ultimately, judge your own risk tolerance by how much you trust the source, how much you want the software, what kind of systems protection you have in place (antivirus, antimalware, permissions control, backups), and how much you can afford to have your system compromised. Thanks for this! I finally decided to hand the matter over to my friend, because vetting the binaries are just... a whole project on(in?) its own. I sent them exactly what you wrote, in addition to some concrete guidance on how to setup VMs, create backups, bootable media, whathaveyou.