So, what should I make of this?
So, what should I make of this?
This was posted, willingly, by "haxNode" on 1337x. At the bottom of his uploads, like usual, but this seems really bad. Is it just a severe overreaction to the keygen? Am I right not to trust haxNode, even in 1337x? What do you guys think?
Looking at the behaviour, this is some really shady piece of software, changing credentials, adding scheduled tasks as an admin, etc.
Avoid.
haxNode - Caught with malware
mentioned in FMHY's unsafe list
Which url did you use for 1337x? There are lots of copies there just serve malware
Most people stick to 1337x .to
But .to isn't 100% safe either. Just worth asking
Not going to tell you it's safe but if its a keygen they've always been flagged by most antivirus and I wouldn't be surprised if there was an actual patch needed for a keygen to work.
To be fair though I don't know enough about the whole situation and I'd say go with your gut or test it in a vm or similar .
Patchers are inherently suspicious to AVs (they write to executable files) and VirusTotal by extension. Most of these detections only say “HackTool”, which may not mean the file harms your computer – the security community is usually unwilling to inspect DRM circumvention tools any further because there is negative financial and reputational gain from helping pirates if you work for a security vendor.
This explains why the VirusTotal community is split. I would be more trusting of the software if it were open source, which it understandably isn’t. Based on the VirusTotal community comments, I lean 70% false positive / 30% malware, which may not be a probability you’re willing to risk for obtaining free desktop management software (at least I’m not).
However, haxNode·net is a website that has a reputation to uphold, and I’m not going to investigate its history for you. I would significantly alter my verdict if trusted piracy communities like FMHY speak against or in favor of it.
In conclusion: Do more research. Run at your own risk.
I've always used .to
That's never been an issue before for me. All the software posts now are either haxNode or crackshash. It's dissapointing.
I wouldn't trust it. If you have to get a key then do it in a non networked VM . screenshot the key from the host and then delete the VM.
I can't say for sure if it's secure, but keygens have been the target of previous warnings from antivirus software, and it wouldn't shock me if a patch was necessary for a keygen to work basketball stars