sha256_hash in the forensic JSON export is fake | Level 3

[ameyvaidya44]

The exportForensicJSON() function in dashboard.js generates a forensic report that includes a field called sha256_hash. The value is constructed as:

sha256_hash: 3A7C${Math.random().toString(16).substr(2, 12).toUpperCase()}

This is not a real hash of anything. It is a hardcoded prefix "3A7C" followed by random hex characters. It has no cryptographic relationship to the file that was analyzed, the scan results, or any other data in the report.

This is a serious problem for a tool explicitly marketed for forensic use and "legal admissibility."

I would like to work on this issue, please consider assigning this to me!!

[Madhu-T18]

I reviewed the exportForensicJSON() implementation in dashboard.js and noticed that the sha256_hash field is currently generated using:

sha256_hash: `3A7C${Math.random().toString(16).substr(2, 12).toUpperCase()}`

This produces a random hexadecimal string rather than an actual SHA-256 digest derived from the analyzed file or report contents.

Because the exported report is intended for forensic use, this may create confusion regarding data integrity and authenticity.

I would like to work on replacing this with a real SHA-256 hash generated from the analyzed file/report data and ensure the implementation is deterministic and verifiable.

Please consider assigning this issue to me.

[Muskankr]

Hi @sutanjoyb , I would like to work on this issue as NSOC'26 Contributor. Could you please assign this to me?