# Multi-Hasher (mhash)

Run without a commandline option to get an overview of supported hashes and functions

    $ mhash
    MultiHasher - (c) by ROSE SWE, Ralph Roth

    ==| MultiHasher - A versatile file hash calculator by ROSE SWE, Ralph Roth

    ==| Usage:
      mhash   <file1> <file2> ... <fileN>

    ==| Description:
      This program calculates a variety of cryptographic hashes for each file provided.

      Supported algorithms include:
      - MD4          (128-bit)  Fast but weak, deprecated
      - MD5          (128-bit)  Widely used, but vulnerable
      - SHA1         (160-bit)  Collisions found, not recommended
      - SHA256       (256-bit)  Secure, widely used
      - SHA384       (384-bit)  Secure, part of SHA-2
      - SHA512       (512-bit)  Secure, SHA-2 family
      - SHA3-224     (224-bit)  Keccak-based, secure
      - SHA3-256     (256-bit)  More secure than SHA-2
      - SHA3-384     (384-bit)  Stronger alternative to SHA-384
      - SHA3-512     (512-bit)  Strongest Keccak-based hash

      - Adler32      (32-bit)   Very fast, not for cryptography
      - CRC32        (32-bit)   Common in file checksums, weak

      - XXH32        (32-bit)   Extremely fast, non-cryptographic
      - XXH64        (64-bit)   Faster, used for checksums
      - RIPEMD160    (160-bit)  Alternative to SHA-1
      - BLAKE2b-256  (256-bit)  Faster than SHA-3, highly secure
      - BLAKE2b-512  (512-bit)  Faster than SHA-3, highly secure (b2sum)
      - BLAKE3       (256-bit)  Very fast, parallelizable

    ==| Examples:
      To calculate the hashes of file1.txt and file2.txt, run:

      	  mhash file1.txt file2.txt

## False Positives

False Positive Detections: Microsoft Defender is incorrectly flagging the following items as malware within the Windows executable file. These detections are, in fact, false positives caused by the way Defender interprets the executable’s compression:

- Program:Win32/Wacapew.C!ml
- Program:Win32/Cayunamer.A!ml
- Trojan:Win32/Wacatac.H!ml
- Trojan:Win32/Wacatac.C!ml

The compression technique (UPX) used in the executable appears to trigger these erroneous alerts.

/* END */