Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem: T1562.001 Atomic Test #12 - Uninstall Sysmon --> Failed #2952

Open
SirStephanikus opened this issue Oct 6, 2024 · 6 comments
Open
Assignees

Comments

@SirStephanikus
Copy link

SirStephanikus commented Oct 6, 2024

What did you do?

Invoke-AtomicTest T1562.001 -TestNumbers 12 -CheckPrereqs
PathToAtomicsFolder = C:\AtomicRedTeam\atomics

CheckPrereq's for: T1562.001-12 Uninstall Sysmon
Prerequisites met: T1562.001-12 Uninstall Sysmon

Invoke-AtomicTest T1562.001 -TestNumbers 12 -Verbose

What did you expect to happen?

After the -CheckPrereqs Test met all prerequisites, the AtomicTest should uninstall sysmon correctly,

What happened instead?

Uninstaller does not find sysmon, despite being installed and active.
Aborting uninstall: Sysmon service named Sysmon is not installed, but Sysmon driver named SysmonDrv is.

Your Environment

Windows Server 2022 Standard, as an AD-DC. Run with privileged user.

I found the issue:
---> The Atomic test expects to find "sysmon", but it runs here as "sysmon64" (installed via chocolatey).

Proof:

Get-Service -Name Sysmon64

Status   Name               DisplayName
------   ----               -----------
Running  Sysmon64           Sysmon64
sc.exe query sysmon64 | findstr sysmon64

SERVICE_NAME: sysmon64

Suggestion, fix up the Atomic-Test to recognize even sysmon64.
See also #2951

@NChilds86
Copy link

Nice work with the committed find and thanks for reposting the feedback and the proof and team will have this resolved soon as it is possible.

Thanks mate....

Copy link

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added the Stale label Nov 24, 2024
@SirStephanikus
Copy link
Author

Stale prevention:
Any news on this?

@github-actions github-actions bot removed the Stale label Nov 25, 2024
@cyberbuff cyberbuff self-assigned this Nov 26, 2024
@cyberbuff
Copy link
Collaborator

Hello @SirStephanikus Sorry for the delay. I am working on a fix for both of your issues (#2951 and #2952). Should be fixed within end of the week. Thanks for your patience.

Copy link

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added the Stale label Dec 27, 2024
@SirStephanikus
Copy link
Author

Push, to remove stale label

@github-actions github-actions bot removed the Stale label Dec 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants