starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Bug Report - Malicious activity detected - Windows process wrong location #2096

New Issue
Closed
opened 2026-01-30 22:46:41 +00:00 by claunia · 1 comment
claunia commented 2026-01-30 22:46:41 +00:00
Owner
Copy Link

Originally created by @cypherstream on GitHub (Jun 24, 2019).

After installind and runnign the Microsoft Terminal Preview, Dell Secureworks opened a ticket with the following informaiton below. Is this safe to run?

We've observed potentially malicious activity, Windows process wrong location, (process: conhost.exe, process MD5: 7a8c227929a1047e2120422da75d231b) for user (redacted) on host (redacted). The detection was performed by SecureWorks CTU threat indicators and we are escalating this activity to you based on our default event handling policies.

Process Name: conhost.exe
Process MD5: 7a8c227929a1047e2120422da75d231b
Command Line: conhost.exe --headless --width 120 --height 30 --signal 0x840 -- powershell.exe
Parent Process Name: windowsterminal.exe
Process Start Time: 2019-06-24T13:51:34.357Z
Last Process Activity Time: 2019-06-24T13:53:06.034Z

Threat Intel Feed Information

Threat Intel Feed Report: Windows process wrong location
Threat Intel Feed Update Time: 2018-09-30T22:43:59.000Z
Classification: opportunistic trojan
Description: A process with a common Windows process name was identified running from a non-standard location on the system. This is considered unusual behavior because a process by this name is expected to be run from the %system% directory. It is common for malware to use the same name as legitimate Windows processes in an attempt to blend in when running processes are inspected.

Examples:

c:\windows\csrss.exe
%temp%\lsass.exe

Targeted threat actors may also use this technique to hide their malware on the compromised system.

Originally created by @cypherstream on GitHub (Jun 24, 2019). After installind and runnign the Microsoft Terminal Preview, Dell Secureworks opened a ticket with the following informaiton below. Is this safe to run? We've observed potentially malicious activity, Windows process wrong location, (process: conhost.exe, process MD5: 7a8c227929a1047e2120422da75d231b) for user (redacted) on host (redacted). The detection was performed by SecureWorks CTU threat indicators and we are escalating this activity to you based on our default event handling policies. Process Name: conhost.exe Process MD5: 7a8c227929a1047e2120422da75d231b Command Line: conhost.exe --headless --width 120 --height 30 --signal 0x840 -- powershell.exe Parent Process Name: windowsterminal.exe Process Start Time: 2019-06-24T13:51:34.357Z Last Process Activity Time: 2019-06-24T13:53:06.034Z ---------------------------------------------- Threat Intel Feed Information ---------------------------------------------- Threat Intel Feed Report: Windows process wrong location Threat Intel Feed Update Time: 2018-09-30T22:43:59.000Z Classification: opportunistic trojan Description: A process with a common Windows process name was identified running from a non-standard location on the system. This is considered unusual behavior because a process by this name is expected to be run from the %system% directory. It is common for malware to use the same name as legitimate Windows processes in an attempt to blend in when running processes are inspected. Examples: > c:\windows\csrss.exe > %temp%\lsass.exe Targeted threat actors may also use this technique to hide their malware on the compromised system.
claunia added the Needs-TriageNeeds-Tag-FixResolution-Duplicate labels 2026-01-30 22:46:41 +00:00
claunia commented 2026-01-30 22:46:42 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jun 24, 2019):

Dell Secureworks is too trigger-happy here. We have an executable named conhost.exe, which SecureWorks has detected as being a system application based on name alone. That's never going to be a winning strategy.

@DHowett-MSFT commented on GitHub (Jun 24, 2019): Dell Secureworks is too trigger-happy here. We have an executable named `conhost.exe`, which SecureWorks has detected as being a system application _based on name alone_. That's never going to be a winning strategy.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Needs-Tag-Fix Needs-Triage Resolution-Duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#2096
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?