File mfcm140u.dll

Size 73.4KB
Type PE32 executable (DLL) (GUI) Intel 80386 Mono/.Net assembly, for MS Windows
MD5 2573e505166eea3c706aedfd5afabbb0
SHA1 29b290ea7c5b0dff8f422e80d1b56ac2f15791bf
SHA256 fd19ce03d9474b57bd38c59ee6598d636156fa8c4f157e418ad82b867683f9b7
SHA512
a232ddae93c0579407d0be4ef35e5176207043ce14d5eba6108d3930d37f57c758377b1e9bdfc51b8cea38a0207f263b0a824e125bb4844fff36a7dc955b4407
CRC32 F5776B75
ssdeep None
PDB Path d:\a01\_work\2\s\\binaries\x86ret\bin\i386\\MFCM140U.i386.pdb
Yara
  • anti_dbg - Checks if being debugged

Score

This file appears fairly benign with a score of 0.3 out of 10.

Please notice: The scoring system is currently still in development and should be considered an alpha feature.


Feedback

Expecting different results? Send us this analysis and we will inspect it. Click here

Information on Execution

Analysis
Category Started Completed Duration Routing Logs
FILE June 24, 2025, 1:04 p.m. June 24, 2025, 1:11 p.m. 395 seconds internet Show Analyzer Log
Show Cuckoo Log

Analyzer Log

2025-06-24 12:23:30,030 [analyzer] DEBUG: Starting analyzer from: C:\tmpj6atou
2025-06-24 12:23:30,030 [analyzer] DEBUG: Pipe server name: \??\PIPE\ieVgELdIHnMHLhGApgaV
2025-06-24 12:23:30,030 [analyzer] DEBUG: Log pipe server name: \??\PIPE\FdgiAJJtyLbhtDQZI
2025-06-24 12:23:30,358 [analyzer] DEBUG: Started auxiliary module Curtain
2025-06-24 12:23:30,375 [analyzer] DEBUG: Started auxiliary module DbgView
2025-06-24 12:23:30,983 [analyzer] DEBUG: Started auxiliary module Disguise
2025-06-24 12:23:31,203 [analyzer] DEBUG: Loaded monitor into process with pid 504
2025-06-24 12:23:31,203 [analyzer] DEBUG: Started auxiliary module DumpTLSMasterSecrets
2025-06-24 12:23:31,203 [analyzer] DEBUG: Started auxiliary module Human
2025-06-24 12:23:31,203 [analyzer] DEBUG: Started auxiliary module InstallCertificate
2025-06-24 12:23:31,203 [analyzer] DEBUG: Started auxiliary module Reboot
2025-06-24 12:23:31,265 [analyzer] DEBUG: Started auxiliary module RecentFiles
2025-06-24 12:23:31,265 [analyzer] DEBUG: Started auxiliary module Screenshots
2025-06-24 12:23:31,280 [analyzer] DEBUG: Started auxiliary module Sysmon
2025-06-24 12:23:31,280 [analyzer] DEBUG: Started auxiliary module LoadZer0m0n
2025-06-24 12:23:31,342 [lib.api.process] ERROR: Failed to execute process from path u'C:\\Users\\ADMINI~1\\AppData\\Local\\Temp\\mfcm140u.dll' with arguments ['bin\\inject-x86.exe', '--app', u'C:\\Users\\ADMINI~1\\AppData\\Local\\Temp\\mfcm140u.dll', '--only-start', '--curdir', 'C:\\Users\\ADMINI~1\\AppData\\Local\\Temp'] (Error: Command '['bin\\inject-x86.exe', '--app', u'C:\\Users\\ADMINI~1\\AppData\\Local\\Temp\\mfcm140u.dll', '--only-start', '--curdir', 'C:\\Users\\ADMINI~1\\AppData\\Local\\Temp']' returned non-zero exit status 1)

Cuckoo Log

2025-06-24 13:04:34,574 [cuckoo.core.scheduler] DEBUG: Task #6629401: no machine available yet
2025-06-24 13:04:35,612 [cuckoo.core.scheduler] DEBUG: Task #6629401: no machine available yet
2025-06-24 13:04:36,640 [cuckoo.core.scheduler] DEBUG: Task #6629401: no machine available yet
2025-06-24 13:04:37,669 [cuckoo.core.scheduler] DEBUG: Task #6629401: no machine available yet
2025-06-24 13:04:38,699 [cuckoo.core.scheduler] DEBUG: Task #6629401: no machine available yet
2025-06-24 13:04:39,726 [cuckoo.core.scheduler] DEBUG: Task #6629401: no machine available yet
2025-06-24 13:04:40,797 [cuckoo.core.scheduler] DEBUG: Task #6629401: no machine available yet
2025-06-24 13:04:41,872 [cuckoo.core.scheduler] DEBUG: Task #6629401: no machine available yet
2025-06-24 13:04:43,081 [cuckoo.core.scheduler] DEBUG: Task #6629401: no machine available yet
2025-06-24 13:04:44,299 [cuckoo.core.scheduler] DEBUG: Task #6629401: no machine available yet
2025-06-24 13:04:45,342 [cuckoo.core.scheduler] DEBUG: Task #6629401: no machine available yet
2025-06-24 13:04:46,390 [cuckoo.core.scheduler] DEBUG: Task #6629401: no machine available yet
2025-06-24 13:04:47,414 [cuckoo.core.scheduler] DEBUG: Task #6629401: no machine available yet
2025-06-24 13:04:48,914 [cuckoo.core.scheduler] DEBUG: Task #6629401: no machine available yet
2025-06-24 13:04:50,062 [cuckoo.core.scheduler] DEBUG: Task #6629401: no machine available yet
2025-06-24 13:04:51,210 [cuckoo.core.scheduler] DEBUG: Task #6629401: no machine available yet
2025-06-24 13:04:52,274 [cuckoo.core.scheduler] DEBUG: Task #6629401: no machine available yet
2025-06-24 13:04:53,343 [cuckoo.core.scheduler] DEBUG: Task #6629401: no machine available yet
2025-06-24 13:04:54,401 [cuckoo.core.scheduler] DEBUG: Task #6629401: no machine available yet
2025-06-24 13:04:55,467 [cuckoo.core.scheduler] DEBUG: Task #6629401: no machine available yet
2025-06-24 13:04:56,748 [cuckoo.core.scheduler] INFO: Task #6629401: acquired machine win7x6416 (label=win7x6416)
2025-06-24 13:04:56,752 [cuckoo.core.resultserver] DEBUG: Now tracking machine 192.168.168.216 for task #6629401
2025-06-24 13:04:57,600 [cuckoo.auxiliary.sniffer] INFO: Started sniffer with PID 1989596 (interface=vboxnet0, host=192.168.168.216)
2025-06-24 13:04:58,124 [cuckoo.machinery.virtualbox] DEBUG: Starting vm win7x6416
2025-06-24 13:04:58,749 [cuckoo.machinery.virtualbox] DEBUG: Restoring virtual machine win7x6416 to vmcloak
2025-06-24 13:07:58,533 [cuckoo.core.guest] INFO: Starting analysis #6629401 on guest (id=win7x6416, ip=192.168.168.216)
2025-06-24 13:07:59,541 [cuckoo.core.guest] DEBUG: win7x6416: not ready yet
2025-06-24 13:08:04,608 [cuckoo.core.guest] INFO: Guest is running Cuckoo Agent 0.10 (id=win7x6416, ip=192.168.168.216)
2025-06-24 13:08:04,730 [cuckoo.core.guest] DEBUG: Uploading analyzer to guest (id=win7x6416, ip=192.168.168.216, monitor=latest, size=6660546)
2025-06-24 13:08:06,382 [cuckoo.core.resultserver] DEBUG: Task #6629401: live log analysis.log initialized.
2025-06-24 13:08:07,529 [cuckoo.core.resultserver] DEBUG: Task #6629401 is sending a BSON stream
2025-06-24 13:08:08,781 [cuckoo.core.resultserver] DEBUG: Task #6629401: File upload for 'shots/0001.jpg'
2025-06-24 13:08:08,793 [cuckoo.core.resultserver] DEBUG: Task #6629401 uploaded file length: 133592
2025-06-24 13:08:08,930 [cuckoo.core.guest] WARNING: win7x6416: analysis #6629401 caught an exception
Traceback (most recent call last):
  File "C:/tmpj6atou/analyzer.py", line 824, in <module>
    success = analyzer.run()
  File "C:/tmpj6atou/analyzer.py", line 673, in run
    pids = self.package.start(self.target)
  File "C:\tmpj6atou\modules\packages\exe.py", line 34, in start
    return self.execute(path, args=shlex.split(args))
  File "C:\tmpj6atou\lib\common\abstracts.py", line 205, in execute
    "Unable to execute the initial process, analysis aborted."
CuckooPackageError: Unable to execute the initial process, analysis aborted.

2025-06-24 13:08:08,942 [cuckoo.core.plugins] DEBUG: Stopped auxiliary module: Redsocks
2025-06-24 13:08:08,968 [cuckoo.core.plugins] DEBUG: Stopped auxiliary module: Sniffer
2025-06-24 13:08:10,142 [cuckoo.machinery.virtualbox] INFO: Successfully generated memory dump for virtual machine with label win7x6416 to path /srv/cuckoo/cwd/storage/analyses/6629401/memory.dmp
2025-06-24 13:08:10,144 [cuckoo.machinery.virtualbox] DEBUG: Stopping vm win7x6416
2025-06-24 13:11:09,939 [cuckoo.core.resultserver] DEBUG: Stopped tracking machine 192.168.168.216 for task #6629401
2025-06-24 13:11:09,941 [cuckoo.core.resultserver] DEBUG: Cancel <Context for LOG> for task 6629401
2025-06-24 13:11:10,364 [cuckoo.core.scheduler] DEBUG: Released database task #6629401
2025-06-24 13:11:10,390 [cuckoo.core.scheduler] INFO: Task #6629401: analysis procedure completed

Signatures

Yara rule detected for file (1 event)
description Checks if being debugged rule anti_dbg
This executable has a PDB path (1 event)
pdb_path d:\a01\_work\2\s\\binaries\x86ret\bin\i386\\MFCM140U.i386.pdb
Screenshots
Name Response Post-Analysis Lookup
No hosts contacted.
IP Address Status Action VT Location
No hosts contacted.
Cuckoo

We're processing your submission... This could take a few seconds.