GridinSoft Threat Intelligence

redshift4max.dlr file report

Under review File reputation report
MD5 5851daadca97c53b251e440f2bdf9c4f
Latest seen 2024-07-02 23:00:57 (2 years ago)
First seen 2024-07-02 23:00:57 (2 years ago)
Size 8 MB
Publisher Autodesk, Inc.
Product 3ds Max

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2024-07-02 23:00:57 (2 years ago); latest analysis 2024-07-02 23:00:57 (2 years ago).

Publisher context

Company metadata: Autodesk, Inc.. Product metadata: 3ds Max.

Observed locations

ThreatInfo has seen this file in user or system paths listed below. Unexpected locations increase the need for local verification.

Recommended action

What to do next

  1. Use the hash and metadata below to verify the exact file identity.
  2. Review publisher, signature, paths, and PE details for inconsistencies.
  3. Run a local scan if the file appears unexpectedly or starts with Windows.

redshift4max.dlr is a Windows file recorded in the ThreatInfo database. It is associated with 3ds Max. The reported company name is Autodesk, Inc.. The current detection status is Undefined, based on the latest analysis from 2024-07-02 23:00:57 (2 years ago).

ThreatInfo does not have a final classification for this file yet. Use the technical details below to compare the hash, size, signature, and observed locations with the copy found on your device.

Product Name: 3ds Max
Company Name: Autodesk, Inc.
MD5: 5851daadca97c53b251e440f2bdf9c4f
Size: 8 MB
First Published: 2024-07-02 23:00:57 (2 years ago)
Latest Published: 2024-07-02 23:00:57 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-07-02 23:00:57 (2 years ago)
%commonappdata%\redshift\plugins\3dsmax\2023

ThreatInfo has observed redshift4max.dlr in the locations listed above. Files found in temporary folders, user profile folders, startup locations, or unusual application directories should be reviewed more carefully than files installed under a known program directory.

Windows 10 100.0%

The most common operating system signal for redshift4max.dlr is Windows 10 with 100.0% of observed hits. If your system differs from the common profile, check whether the file was introduced by a specific installer, archive, or removable device.

redshift4max.dlr is identified as pe for 64-bit systems. The subsystem is Windows GUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.

Format pe
Architecture 64-bit
Subsystem Windows GUI
Entry point 0x00431b40
Image base 0x0000000180000000

PE Sections:

Sections 7
Raw data 9133056

Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.

.text 4701696 bytes · 51.5% of section data
MD5 f52718bdb7dac624687e5de3c0b70505
.rdata 2583040 bytes · 28.3% of section data
MD5 f78ad0c5647c8dd3bae16b58aa9964bf
.data 642048 bytes · 7.0% of section data
MD5 855d627b6edae8dffa4bcb86ec9de925
.pdata 164864 bytes · 1.8% of section data
MD5 b3ead9a309cad717c7387ab471838dbf
_RDATA 512 bytes · 0.0% of section data
Uncommon name
MD5 fc2f14d81e335ad78fd3a2189af093b9
.rsrc 777216 bytes · 8.5% of section data
MD5 c477d038877f6f1ad7ce17ae719e72d1
.reloc 263680 bytes · 2.9% of section data
MD5 5851848ded1b1ef961faa229104c121c

PE section names and hashes can reveal packing, injected resources, or unusual build artifacts. Sections with uncommon names, very large raw data, or hashes that differ from a trusted copy deserve additional review.

Report conclusion

This file is still under review

ThreatInfo has not assigned a final verdict yet. Compare the file hash, location, signature, and publisher before trusting the file on a production system.

Scan with GridinSoft Anti-Malware Use a local scan if the file origin or behavior is unclear. Check this hash on VirusTotal

Recommended next steps

  • Compare the local file MD5 with 5851daadca97c53b251e440f2bdf9c4f.
  • Check the file path, publisher, and signature against the details in this report.
  • Run a GridinSoft scan if the source, path, or behavior looks unusual.