GridinSoft Threat Intelligence

redshift4max.dlr file report

Under review File reputation report
MD5 a839a48a183e0f2dc5505af5d7f2a358
Latest seen 2024-07-02 23:00:58 (2 years ago)
First seen 2024-07-02 23:00:58 (2 years ago)
Size 10 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:58 (2 years ago); latest analysis 2024-07-02 23:00:58 (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:58 (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: a839a48a183e0f2dc5505af5d7f2a358
Size: 10 MB
First Published: 2024-07-02 23:00:58 (2 years ago)
Latest Published: 2024-07-02 23:00:58 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-07-02 23:00:58 (2 years ago)
%commonappdata%\redshift\plugins\3dsmax\2019

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 0x00497be4
Image base 0x0000000180000000

PE Sections:

Sections 9
Raw data 10667520

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

.text 5283328 bytes · 49.5% of section data
Large raw data
MD5 5e6d4c309bf422844f0366016ab101fc
.rdata 3463168 bytes · 32.5% of section data
MD5 191f145a0a7bee050e2cbc63afd88a59
.data 606208 bytes · 5.7% of section data
MD5 435239b1803c5cb0962ed2eca5672f68
.pdata 237568 bytes · 2.2% of section data
MD5 524c70e8bf1916e17560934f789639db
.gfids 512 bytes · 0.0% of section data
Uncommon name
MD5 1411b7587a7e8ce74839ce7d42783d7d
.tls 512 bytes · 0.0% of section data
MD5 1f354d76203061bfdd5a53dae48d5435
_RDATA 35328 bytes · 0.3% of section data
Uncommon name
MD5 7915234633a6d81857aaafc5a5b03883
.rsrc 777216 bytes · 7.3% of section data
MD5 fc26ec1d9d3945c0e21bc6f0fd7fe679
.reloc 263680 bytes · 2.5% of section data
MD5 432d9f3805d2073d1082e2d64b058c4b

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 a839a48a183e0f2dc5505af5d7f2a358.
  • 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.