#1
Jun 15, 2026
Hunt Splunk sidecar recovery abuse that writes files and spawns shells
Hypothesis: An unauthenticated attacker abuses Splunk sidecar recovery endpoints to write outside backup paths, then executes code under the Splunk service account.
Why it matters: CISA KEV makes this current, but the hunt is not an exposure check. The discriminator is the exploit chain on the Splunk host: recovery/backup path, blank Basic auth, backupFile traversal, file writes outside backup directories, and service-account shell or script execution.
Starter hunt: Start in CloudTrail, DNS/HTTP logs, and identity sign-in logs. On Splunk Enterprise hosts, hunt endpoint URL or process telemetry for /en-US/splunkd/__raw/v1/postgres/recovery/backup or /v1/postgres/recovery/backup with Authorization: Basic Og== or backupFile=../. Correlate splunkd, postgres, or pg_dump writing outside backup paths with sh, bash, python, cmd.exe, or powershell.exe under the Splunk service account...
Endpoint
T1190
T1059
T1105
T1565.001
Source: CVE-2026-20253: CISA Warns of Actively Exploited Splunk Enterprise RCE
#2
Jun 15, 2026
Hunt RoguePlanet Defender race that gives a user SYSTEM
Hypothesis: An adversary abuses a Defender race so MsMpEng.exe or WinDefend spawns a SYSTEM shell or LOLBin tree from user-writable path activity, then runs discovery or tampering commands.
Why it matters: Malwarebytes reported a public CVE-2026-50656 exploit and Microsoft confirmed a fix is still in progress. The discriminator is not Defender noise. It is an interactive shell or LOLBin tree with MsMpEng.exe parentage and a SYSTEM token after user-writable path race activity.
Starter hunt: Start in EDR process/file telemetry. Pivot on MsMpEng.exe or WinDefend spawning cmd.exe, powershell.exe, wscript.exe, cscript.exe, rundll32.exe, reg.exe, schtasks.exe, sc.exe, or net.exe as SYSTEM from a user-writable path. Correlate with RoguePlanet.exe execution or reparse point activity in the prior 10 minutes, then follow the child tree for Add-MpPreference, service creation, admin group changes, or whoami /all.
Endpoint
T1068
T1059.003
T1059.001
T1562.001
Source: Microsoft working on a fix for RoguePlanet, a flaw that grants full PC control
#3
Jun 15, 2026
Hunt @mastra easy-day-js postinstall that drops a stealer
Hypothesis: A compromised npm contributor account publishes easy-day-js with a postinstall hook that disables TLS validation, downloads a second stage, and reads developer credential stores.
Why it matters: snyk source reporting ties this to observed TTPs. This is not a package-presence hunt. The durable discriminator is the install-time process lineage: node or npm executing easy-day-js setup.cjs, TLS disabled through NODE_TLS_REJECT_UNAUTHORIZED, raw IP download, marker files, hidden temp execution, then credential store reads.
Starter hunt: Start in EDR process/file telemetry on developer workstations and CI/CD audit logs. On developer workstations and CI runners, hunt npm, pnpm, yarn, node, or a CI process executing easy-day-js setup.cjs. Require the postinstall child process to set NODE_TLS_REJECT_UNAUTHORIZED, write ~/.pkg_history or ~/.pkg_logs, connect to 23.254.164.92:8000/update/49890878, spawn a detached temp payload, or read credential stores.
Endpoint
T1195.002
T1059.007
T1105
T1552
T1005
Source: A Forgotten Contributor Account Compromised the Entire Mastra npm Package Scope
#4
Jun 15, 2026
Hunt DragonForce Backdoor.Turn injected into DbgView64
Hypothesis: DragonForce stages Backdoor.Turn through VirtualBox DLL hijacking and DbgView64 injection, then uses Teams TURN relay traffic while performing LDAP search, credential access, or lateral movement.
Why it matters: This is better than a generic Teams traffic hunt. The source names Backdoor.Turn, DbgView64.exe, vboxrt.dll, vulnerable driver loading, LDAP search, browser credential access, and Teams TURN relay use in the same intrusion chain.
Starter hunt: Start in EDR process/file telemetry. Pivot on DbgView64.exe making Teams or Skype TURN relay connections, then performing LDAP queries, spawning shells, reading browser credential stores, or starting remote execution. Correlate with nearby VirtualBox vboxrt.dll sideloading and vulnerable driver loads.
Endpoint
T1574.001
T1068
T1562.001
T1055
T1059
T1087.002
Source: Cybercriminals mask malicious communications through Microsoft Teams relays
#5
Jun 15, 2026
Hunt forged SimpleHelp OIDC technician access that launches endpoint scripts
Hypothesis: An adversary forges a SimpleHelp OIDC technician session, then launches shells or scripts on managed endpoints without the matching identity sign-in or MFA event.
Why it matters: The durable discriminator is the ordered telemetry chain, not a generic artifact. Field Effect's CVE-2026-48558 writeup gives the useful shape: forged OIDC tokens, privileged technician creation, MFA bypass in affected configs, and remote access to managed endpoints. The hunt does not ask whether SimpleHelp is approved. It looks for endpoint execution missing the identity event that should precede it.
Starter hunt: Start in CloudTrail, DNS/HTTP logs, and identity sign-in logs. Pivot on SimpleHelp server or agent processes that spawn cmd.exe, powershell.exe, pwsh, wscript, cscript, mshta, bash, sh, curl, or wget on managed endpoints when Entra shows no matching successful sign-in or MFA event to the SimpleHelp app. Raise priority when the same lineage runs whoami /all, nltest, net group, Get-ADUser, az, gcloud, aws sts, kubec...
Endpoint
T1550
T1550.001
T1136
T1078
T1219
T1059
Source: SimpleHelp flaw could enable broader compromise across managed environments
#6
Jun 15, 2026
Hunt Gentlemen EDR killer staging before ransomware deployment
Hypothesis: Gentlemen affiliates stage EDR killer tools, create or load driver services from non-vendor paths, terminate security processes, and run backup-deletion or ransomware-prep commands.
Why it matters: ESET's research, reported by CSO, ties the Gentlemen affiliate kit to EDR killer tooling for hundreds of security processes. The clearest hunting angle is the sequence, not the driver name by itself: named kit artifacts, vulnerable driver loading, security tool tampering, then pre-encryption commands.
Starter hunt: Start in EDR process/file telemetry. Pivot on process ancestry where GentleKiller, HexKiller, ThrottleBlood, HavocKiller, or OxideHarvest creates a driver service or loads googleApiUtil64.sys, ThrottleBlood.sys, Baidu BdApi, or Huawei audio driver components from ProgramData, Temp, Users, or Downloads. Require follow-on taskkill, sc stop, fltmc unload, wevtutil cl, vssadmin delete shadows, wbadmin, or bcdedit.
Endpoint
T1562.001
T1068
T1543.003
T1490
T1486
Source: Threat actor adds advanced ‘EDR killer’ tools to ransomware-as-a-service platform
#7
Jun 15, 2026
Hunt Sinobi service hijack that turns cbdefense into C:\ProgramData\bin.exe
Hypothesis: Sinobi operators create a fallback Assistance admin account, hijack the cbdefense service to run C:\ProgramData\bin.exe after reboot, then use rclone before encryption.
Why it matters: picussecurity source reporting ties this to observed TTPs. The durable discriminator is the ordered chain: Assistance account creation, cbdefense service tampering, reboot, services.exe launching a user-writable payload, then rclone staging and .SINOBI or README.txt file activity. That chain carries the malicious-vs-benign discriminator inside the telemetry.
Starter hunt: Start in EDR process/file telemetry. Pivot on net.exe or cmd.exe creating Assistance, then sc.exe changing cbdefense start= disabled or binpath= C:\programdata\bin.exe, followed by shutdown /r /t 0, services.exe launching that payload, rclone.exe using c:\programdata\rclone-ssh.conf with --max-age=2y, and .SINOBI or README.txt file writes.
Endpoint
T1078
T1136.001
T1098
T1562.001
T1543.003
T1048
Source: How Sinobi Ransomware Encrypts Files and Destroys Backups
#8
Jun 15, 2026
Hunt backdoored Checkmarx Jenkins plugin activity that harvests CI secrets
Hypothesis: A backdoored Checkmarx Jenkins AST plugin runs in a Jenkins controller or agent context, reads repository, cloud, Kubernetes, SSH, or API credentials, and uses them for follow-on access.
Why it matters: SOCRadar source reporting ties this to observed CI/CD supply-chain TTPs. The durable discriminator is plugin or Jenkins `java` activity followed by broad secret-file reads, outbound egress, and token use from CI credentials, not a normal plugin update.
Starter hunt: Start in Jenkins controller logs, CI/CD audit logs, and EDR process/file telemetry. Correlate Checkmarx Jenkins AST plugin execution or update with `java`, `sh`, `bash`, `curl`, `wget`, `node`, or `npm` reading `.aws`, `.config/gcloud`, `.azure`, `.kube`, `.ssh`, Jenkins credential stores, or workspace secrets, then outbound GitHub or cloud API use from CI credentials.
Endpoint
T1195.002
T1552.001
T1552.004
T1528
T1083
T1041
Source: May 2026: TeamPCP’s Supply Chain Blitz Hits Checkmarx, GitHub, and npm
#9
Jun 15, 2026
USB shortcut clipper staging JavaScript and renamed Tor
Hypothesis: An adversary uses removable-media shortcuts to stage JavaScript under Public Documents, create scheduled tasks, run renamed Tor locally, and collect clipboard or screenshot data.
Why it matters: Microsoft described an active crypto clipper campaign with removable-media shortcuts, Public Documents JavaScript staging, scheduled tasks, ugate.exe, local Tor proxying, clipboard theft, screenshots, curl uploads, and Defender exclusions. The hunt follows that chain instead of treating USB use or Tor by itself as the signal.
Starter hunt: Start in EDR process/file telemetry. On endpoints, correlate explorer.exe or cmd.exe opening .lnk from removable media to wscript or cscript running C:\Users\Public\Documents\<five-character-folder>\*.js, schtasks task creation, ugate.exe, and localhost:9050 connections. Escalate when clipboard access, screenshots, curl uploads, or Defender exclusions follow.
Endpoint
T1091
T1204.002
T1059.007
T1053.005
T1115
T1113
Source: Crypto Clipper uses Tor and worm-like propagation for persistence and control
#10
Jun 15, 2026
Hunt M365 MFA method enrollment followed by BEC mailbox activity
Hypothesis: An adversary uses an already MFA-satisfied Microsoft 365 session to add a second authentication method, then works the mailbox for BEC without another MFA prompt.
Why it matters: Mitiga saw the attacker enter My Access, change authentication details, and rely on the existing MFA state. The signal is the method change tied to mailbox actions, not a strange login by itself.
Starter hunt: Start in Entra sign-in, audit, Microsoft Graph, and M365 audit logs. Pivot on Microsoft Authenticator or phone-app MFA method registration after an MFA-satisfied sign-in. Within 24 hours require same-user Exchange activity: MailItemsAccessed, inbox-rule changes, forwarding, SendAs, or payment-thread replies.
Identity
T1550
T1556
T1098
T1114
Source: Advisory: Persistent MFA Circumvention in an Advanced BEC Campaign on Microsoft 365 Targets
#11
Jun 15, 2026
Hunt OXLOADER fake Node.js installs that elevate a Storj batch chain
Hypothesis: An adversary uses fake Node.js advertising to deliver a Storj-hosted batch chain that elevates with PowerShell and loads OXLOADER before CASTLESTEALER execution.
Why it matters: elastic.co source reporting ties this to observed TTPs. The hunt follows the delivery chain, not Node.js installation. The discriminators are the named Storj /ruslan/ paths, BATPackageBuilderSetup.bat, aBsvwbdas.exe, -Verb RunAs, and CLR loading from an installer-themed native process.
Starter hunt: Start in EDR process/file telemetry. Pivot on browser or archive downloads of BATPackageBuilderSetup.bat, then cmd.exe or powershell.exe fetching link.storjshare.io/raw/.../ruslan/aBsvwbdas.exe and launching it with -Verb RunAs. Add network pivots for node-js.prentiva99.info and app.miloyannopoulos.com before a native installer process loads CLR or runs CASTLESTEALER.
Endpoint
T1189
T1204.002
T1059.001
T1105
T1036
T1027
Source: Lost in relocation: analysis of a new loader distributing CASTLESTEALER
#12
Jun 15, 2026
Hunt vishing driven MFA changes followed by M365 collection
Hypothesis: A ShinyHunters or Scattered Spider collaborator uses vishing to change MFA or recovery state, then turns the changed identity state into SSO-backed M365 or SaaS collection.
Why it matters: picussecurity source reporting ties this to observed TTPs. This is not a hunt for odd sign-ins. The pivot is an identity control change followed by data collection or OAuth access in the same account or session. Legitimate recovery happens, but recovery that immediately turns into M365 collection is the hunting angle.
Starter hunt: Start in Entra sign-in, audit, Microsoft Graph, and M365 audit logs. Pivot on MFA registration/reset, Temporary Access Pass creation, or password reset followed within 60 minutes by sign-in with the changed method. Require SharePoint, OneDrive, Exchange, eDiscovery, OAuth consent, or Graph activity from a different IP, device, user agent, or app.
Identity
T1566.004
T1078
T1098
T1114.002
T1530
Source: Defending Against ShinyHunters: Tactics and Breaches
#13
Jun 15, 2026
Hunt GentleKiller driver loads followed by security process kills
Hypothesis: Gentlemen ransomware operators stage GentleKiller or related EDR killers, load vulnerable or malicious drivers, and terminate security tools before theft or encryption.
Why it matters: ESET documented the Gentlemen EDR-killer framework and companion tools. The durable discriminator is vulnerable-driver loading paired with multi-product security termination in the same chain, not a driver filename by itself.
Starter hunt: Start in EDR process/file telemetry. Correlate new driver service creation or driver load for `googleApiUtil64.sys`, `ThrottleBlood.sys`, Baidu `BdApi`, Huawei audio driver components, or `.sys` files under `ProgramData`, `Temp`, `Users`, or `Downloads` with follow-on security-process kills from the same host or process chain.
Endpoint
T1562.001
T1068
T1543.003
T1014
T1486
Source: Killing me gently: Inside Gentlemen’s EDR killer framework
#14
Jun 15, 2026
Hunt Dropping Elephant Fondue.exe sideloading from C:\Users\Public
Hypothesis: Dropping Elephant uses a China-themed shortcut to stage payloads under C:\Users\Public, create GoogleErrorReport persistence, and sideload APPWIZ.cpl through Fondue.exe.
Why it matters: Rapid7 gave the artifacts that matter: GoogleErrorReport, Fondue.exe, APPWIZ.cpl in C:\Users\Public, Donut shellcode, and AMSI, WLDP, or ETW patching. That chain separates the hunt from normal Fondue.exe activity.
Starter hunt: Start in EDR process and network telemetry. Pivot on .lnk or document process trees that spawn PowerShell and write to C:\Users\Public. Require a scheduled task named GoogleErrorReport, Fondue.exe loading APPWIZ.cpl from that same path, or AMSI, WLDP, or ETW patching before HTTPS beacons to gcl-power.org or /prjozifvkpkfhkr/gedhagammgjvvva/.
Endpoint
T1204.002
T1059.001
T1053.005
T1574.001
T1620
T1562.001
Source: Malware à la Mode: Tracking Dropping Elephant Tradecraft Through a China-Themed Loader Chain
#15
Jun 15, 2026
Hunt PeopleSoft PSEMHUB staging followed by Azure-themed MeshCentral
Hypothesis: An adversary exploits Oracle PeopleSoft EMHub to stage JSP or XML content under PSEMHUB paths, then uses Azure-themed MeshCentral agents to run commands and read PeopleSoft or WebLogic configs.
Why it matters: GTIG gave path names, filenames, C2 infrastructure, and recon files. The clearest hunting angle is the exploit follow-on chain on the application server, not perimeter logs or a generic vulnerable server list.
Starter hunt: On PeopleSoft or WebLogic servers, search EDR for new JSP files under PSEMHUB.war, files under envmetadata/transactions, or directories named logs, persistantstorage, or scratchpad. Correlate to meshagent32-azure-ops.exe, meshagent64-azure-ops.exe, meshagent64-v2.exe, azurenetfiles.net, psappsrv.cfg, config.xml, or fanout.sh.
Endpoint
T1190
T1059
T1105
T1219
T1083
T1021
Source: ShinyHunters Targets Education Sector with Oracle PeopleSoft Exploit
#16
Jun 15, 2026
ROADrecon style enumeration through legacy Azure AD Graph
Hypothesis: An adversary with a valid Entra token enumerates legacy Azure AD Graph paths across users, groups, apps, service principals, and devices using ROADrecon-style tooling.
Why it matters: Elastic published new coverage for Azure AD Graph Activity Logs, which exposes a directory enumeration path that was hard to see before. ROADrecon, AADInternals, MSOLSpray, and Microburst still use the legacy API, and the hunt keys on the API version, user agent, path breadth, and error pattern rather than the login location or rarity.
Starter hunt: In Azure AD Graph activity logs, find graph.windows.net sessions where one user, app, or IP hits users, groups, servicePrincipals, applications, devices, roles, or oauth2PermissionGrants in a short window with ROADrecon, AADInternals, MSOLSpray, Microburst, PowerShell, Python, FOCI mismatch, or 4xx-heavy probing. Correlate by same user, host, process lineage, request ID, or session.
Identity
T1087.004
T1069.003
T1526
T1580
Source: Azure AD Graph Activity Logs: Ingestion and threat detection to close the visibility gap
#17
Jun 15, 2026
Hunt APT28 DNS rewrites that lead to M365 token replay
Hypothesis: APT28 uses router DNS rewrites to steer Microsoft 365 authentication through adversary infrastructure, then replays the resulting tokens into Exchange or Graph mailbox activity.
Why it matters: Sekoia reported APT28 using compromised routers and DNS rewrites to funnel Microsoft 365 authentication through an adversary-in-the-middle path. The hunt stays in Entra and M365 audit data by looking for token replay tied to concrete mailbox actions, not generic sign-in noise.
Starter hunt: Correlate Entra sign-ins and M365 audit logs for a user who completes browser MFA, then has non-interactive Exchange or Graph activity from a different ASN within 5 to 30 minutes with no fresh MFA prompt. Require MailItemsAccessed, SearchQueryInitiatedExchange, New-InboxRule, Set-InboxRule, or bulk downloads in that same chain.
Identity
T1557
T1528
T1550.001
T1114
Source: APT28, an evolution of tradecraft
#18
Jun 15, 2026
Hunt AUR PKGBUILDs that pull atomic-lockfile or js-digest and touch secrets
Hypothesis: An adversary injects AUR build commands that make yay, paru, or makepkg spawn npm or Bun packages, then reads secrets and writes persistence or eBPF artifacts from the build chain.
Why it matters: Truesec reported injected AUR build commands that pulled those packages and delivered an infostealer and rootkit. The discriminator is secret access or rootkit persistence from the package build process, so it does not depend on knowing which AUR packages a tenant normally uses.
Starter hunt: Start in Linux EDR process/file telemetry and package-manager logs. Pivot on yay, paru, or makepkg spawning npm, npx, bun, or node with atomic-lockfile or js-digest in the command line. Require one child in that lineage to read ~/.npmrc, SSH keys, cloud credential files, browser stores, or .env, then write /etc/systemd/system, /etc/cron.d, /etc/ld.so.preload, /sys/fs/bpf, or make outbound HTTPS.
Endpoint
T1195
T1059
T1552
T1543
T1014
T1105
Source: Supply Chain Attack Compromising Arch Linux AUR Packages with Infostealer and Rootkit
#19
Jun 15, 2026
Hunt RoguePlanet Defender link race to SYSTEM shell
Hypothesis: An adversary abuses Defender link resolution with reparse-point activity so a low-privileged user process leads to a SYSTEM shell without a normal service, task, PsExec, or WMI parent.
Why it matters: The strongest angle is the privilege transition tied to Defender file handling, not a generic SYSTEM shell. Link, hardlink, symlink, junction, or reparse-point creation near Defender scans gives the hunt something concrete to test.
Starter hunt: Start in EDR process/file telemetry. Pivot on low-privileged user processes creating hardlinks, symlinks, junctions, or reparse points in Defender-scanned paths, followed within minutes by cmd.exe, powershell.exe, or conhost.exe running as SYSTEM. Require parentage outside services.exe, taskeng.exe, PsExec, and WMI, then pivot on whoami /priv, net user, sc.exe, or reg.exe.
Endpoint
T1068
T1059.003
T1222
T1562.001
Source: CVE-2026-50656 Microsoft Defender Elevation of Privilege Vulnerability
#20
Jun 15, 2026
Hunt Pink vishing that changes MFA methods before M365 collection
Hypothesis: A vishing operator manipulates Okta or Entra MFA recovery state, then uses the compromised account to collect M365 data and send extortion messages from collaboration tools.
Why it matters: The source gives a full identity to cloud chain: vishing, Okta or Entra phishing kits, MFA bypass, passkey or recovery manipulation, M365 collection, and extortion over compromised collaboration tools. That is specific enough to hunt without asking whether the login is normal.
Starter hunt: Start in Entra sign-in logs, audit logs, Microsoft Graph activity logs, and M365 audit logs. Pivot in Okta or Entra logs, find a successful user sign-in followed within 60 minutes by user-initiated MFA, passkey, FIDO2, or recovery method changes. Require SharePoint or OneDrive bulk access and Exchange or Teams messages with qTox, Tox ID, DLS, ransom, extortion, or 72-hour language from the same account.
Identity
T1598
T1539
T1098
T1528
T1530
T1567
Source: New Data Extortion Group “Pink” Goes Big Game Hunting With Evasive Phishing Kits
#21
Jun 15, 2026
Hunt EvilTokens device code phishing that turns MFA into M365 access
Hypothesis: An adversary uses device-code phishing to make a user complete MFA for the attacker session, then uses the issued tokens to access M365 data or create mailbox persistence.
Why it matters: The discriminator is the chain: Microsoft device code authentication, then cloud access from a separate client or IP using the token issued by that flow. That is huntable in Entra, M365, Exchange, SharePoint, and OneDrive telemetry without asking whether the sign-in is normal for the user.
Starter hunt: Start in Entra sign-in, audit, Microsoft Graph, and M365 audit logs. Pivot on successful device-code authentication to Graph, Exchange, SharePoint, Teams, or OneDrive. Require same-user MailItemsAccessed, file downloads, sync downloads, inbox-rule, or forwarding changes from a non-browser client within 30 minutes.
Identity
T1566
T1528
T1550
T1114
T1530
Source: EvilTokens: A phishing attack that doesn’t steal your password
#22
Jun 15, 2026
Hunt Workspace compliance rules that BCC mail to external inboxes
Hypothesis: An adversary with Google Workspace admin access creates a domain-level compliance or routing rule that silently BCCs targeted mail to an external inbox.
Why it matters: fieldeffect source reporting ties this to observed TTPs. The hunt has concrete pivots: domain-level content compliance or routing changes, BCC or add-recipient actions, the Patroit rule name, the external Gmail sink, and message trace showing copied mail. It does not depend on knowing a normal admin baseline.
Starter hunt: Hunt Google Workspace admin audit logs for domain-level content compliance or routing rules that add BCC, redirect, or add-recipient delivery to external mailboxes. Pivot on Patroit, Patriot misspellings, BebitaBarefoot774@gmail.com, and message traces where matching mail is silently copied.
Identity
T1114.003
T1098
T1567.002
Source: China-nexus actor abuses domain-level compliance rules
#23
Jun 15, 2026
Hunt Tengu exfiltration before vssadmin and .tengu encryption
Hypothesis: Tengu operators use PowerShell, cmd, or rundll32 to stage Rclone or WinSCP exfiltration, then inhibit recovery and mass-rename files with the .tengu extension.
Why it matters: Each tool can be legitimate alone. The source gives the ordered ransomware chain, so the hunt keys on exfiltration, recovery inhibition, log clearing, and the .tengu extension together.
Starter hunt: Search EDR for Rclone or WinSCP activity followed by MEGA connections, then vssadmin shadow copy deletion, wevtutil log clearing, or sc service changes on the same host or account. Escalate when high-volume file writes or renames to .tengu land after those commands.
Endpoint
T1059.001
T1059.003
T1218.011
T1003.001
T1562.001
T1070.001
Source: Tengu Ransomware: Attack Chain From Initial Access to Encryption
#24
Jun 15, 2026
Hunt cloud logging changes followed by concrete access expansion
Hypothesis: An adversary changes AWS CloudTrail or Google Cloud Logging resources to impair audit capture, then creates keys, grants roles, opens storage policy, or reads data in the same window.
Why it matters: Unit 42 names the control plane actions. The clearest hunting angle is exact logging API activity tied to concrete access expansion or data access, not a generic admin change review.
Starter hunt: In CloudTrail and GCP Admin Activity, alert on StopLogging, DeleteTrail, UpdateTrail to an account-external bucket or KMS key, DeleteSink, logging.sinks.update/create to an external destination, or log bucket deletion. Require CreateAccessKey, CreateUser, AttachUserPolicy, SetIamPolicy owner grants, public storage policy changes, or bulk object reads in the same window.
Cloud
T1562.008
T1530
T1526
T1098
Source: Blinding the Watchmen: Abusing Cloud Logging Services for Visibility Loss
#25
Jun 15, 2026
Hunt Entra Agent ID access_agent grants that turn into Graph mailbox actions
Hypothesis: An adversary abuses an Entra access_agent delegated grant and federated identity credential to obtain an agent token that performs mailbox actions through Microsoft Graph.
Why it matters: The durable discriminator is the ordered telemetry chain, not a generic artifact. Red Canary gave the exact Entra and Graph fields needed to separate agent-driven mailbox access from normal user mail. The clearest hunting angle is the access_agent grant tied to the same token lineage as Mail.Send, Mail.ReadWrite, or mailbox settings activity.
Starter hunt: In Entra audit logs, find Add delegated permission grant events where delegated permission grant scope contains access_agent. Join to Graph activity by AppAccessContext.UniqueTokenId or token identifier, then require agentic app token fields plus Mail.Send, Mail.ReadWrite, MailboxSettings.ReadWrite, sendMail, or mailbox settings requests.
Identity
T1098
T1114.002
Source: Investigating suspicious AI workflows in Microsoft Entra Agent ID: Assistive agents
#26
Jun 15, 2026
Hunt AUR PKGBUILD hooks that spawn npm malware and eBPF loading
Hypothesis: An adversary changes orphaned AUR PKGBUILDs so makepkg runs npm or Bun payloads, executes a Rust ELF hook, steals developer secrets, and may load eBPF components.
Why it matters: This is active supply-chain tradecraft with concrete artifacts: AUR package adoption, PKGBUILD changes, atomic-lockfile, js-digest, lockfile-js, the herbsobering npm publisher, a deps ELF hook, and eBPF rootkit behavior. An MDR can hunt the process tree and file events on developer or build hosts.
Starter hunt: Search Linux EDR for makepkg or pacman spawning npm install or bun install, then require atomic-lockfile, js-digest, lockfile-js, or an executable named deps under src/hooks. Escalate if that child reads browser or developer secrets, writes an ELF in a build path, or calls bpf() from the package build chain.
Endpoint
T1195.002
T1059.006
T1204.002
T1554
T1071.001
T1555
Source: Atomic Arch Campaign Hijacks 20+ Linux AUR Packages to Deliver Malware
#27
Jun 15, 2026
Hunt Graph payroll recon chained to broad delegated scopes
Hypothesis: An adversary uses Microsoft Graph directory queries to bulk enumerate users, filter payroll-related fields, and support HR or direct-deposit fraud through broad delegated permissions.
Why it matters: The source names the Graph request path, searched fields, payroll goal, and delegated permissions. That gives a discriminator: bulk Graph directory harvest plus payroll-focused filtering, not a vague bad login.
Starter hunt: In Graph activity logs, find one user or app making requests to /v1.0/users?$top=999, then filter or search requests over displayName, jobTitle, mail, or userPrincipalName for payroll terms with $skiptoken pagination. Correlate by request id and require delegated permissions such as Directory.Read.All or Files.ReadWrite.All.
Identity
T1087
T1114
T1530
T1098
Source: Hackers Use Microsoft Graph Reconnaissance to Target Payroll and HR Employees
#28
Jun 15, 2026
Hunt Microsoft Defender spawning a SYSTEM shell
Hypothesis: An adversary abuses a Microsoft Defender file-processing race so MsMpEng.exe spawns a SYSTEM-integrity shell or LOLBin child after standard-user activity on the same host.
Why it matters: Picus described a direct parent-child and integrity-level pattern. MsMpEng.exe starting cmd, PowerShell, rundll32, reg, or net as SYSTEM is specific enough to hunt without knowing what is normal for the tenant.
Starter hunt: Search EDR process events for MsMpEng.exe spawning cmd.exe, powershell.exe, pwsh.exe, conhost.exe, rundll32.exe, reg.exe, or net.exe with SYSTEM integrity. Correlate to prior standard-user execution on the same host and review descendants for discovery, credential access, persistence, or lateral movement.
Endpoint
T1068
T1059
T1134
Source: RoguePlanet: Anatomy of the Nightmare Eclipse Microsoft Defender Zero-Day
#29
Jun 15, 2026
Hunt phishing-delivered NinjaOne that spawns an interactive shell
Hypothesis: An adversary delivers a preconfigured NinjaOne MSI through phishing, then turns the RMM agent into shell execution, recon commands, and relay traffic from a single endpoint.
Why it matters: The source describes a live RMM abuse chain with phishing delivery, browser fingerprinting, geofencing, hidden download behavior, and a legitimate NinjaOne agent used for remote access. The discriminator is the sequence from click to installer to hands-on-keyboard activity.
Starter hunt: Search EDR for a browser writing an MSI to a user path and msiexec installing it within minutes. Require NinjaRMMAgent.exe or ninja.exe to spawn cmd.exe, powershell.exe, whoami.exe, net.exe, or ipconfig.exe within 30 minutes, plus HTTPS to a NinjaOne relay not seen on other managed endpoints.
Endpoint
T1219
T1566.001
T1204.002
T1059.001
T1059.003
T1071.001
Source: Hackers Abuse NinjaOne RMM Agent to Gain Remote Access to Brazilian Organizations
#30
Jun 15, 2026
Hunt BlueHammer staging EICAR then reading SAM through VSS
Hypothesis: An adversary abuses the BlueHammer Defender update race by staging an EICAR trigger and filesystem redirection, then reads SAM or SYSTEM hives through VSS and gains a SYSTEM shell.
Why it matters: The source gives an ordered exploit chain with Defender update retrieval, EICAR staging, filesystem redirection, VSS hive access, and token elevation. The hunt keys on the sequence, not a vulnerable version or normal Defender updates.
Starter hunt: In Windows EDR, find a non-Defender user process retrieving go.microsoft.com/fwlink/?LinkID=121721&arch=x64, then creating foo.exe with EICAR content, reading SAM or SYSTEM through HarddiskVolumeShadowCopy paths, and spawning cmd.exe or powershell.exe as SYSTEM in the same session. Correlate the activity by same user, host, process lineage, request ID, or session within the source-reported window.
Endpoint
T1068
T1003.002
T1562.001
T1059.003
Source: BlueHammer: The Unpatched Windows Privilege Escalation Exploit
#31
Jun 15, 2026
Hunt ConfigurationRemotingServer.exe spawning a script interpreter after a LNK open
Hypothesis: An adversary uses a self-referencing LNK to trigger Winget DSC, then makes ConfigurationRemotingServer.exe spawn a script interpreter with encoded or download behavior.
Why it matters: Picus documented the Winget DSC self-referencing LNK technique. ConfigurationRemotingServer.exe executing script interpreters is a specific, rare LOLBin abuse named in the source, not normal Winget usage, so it discriminates attacker behavior without needing the customer baseline.
Starter hunt: Start in EDR process telemetry. Pivot on ConfigurationRemotingServer.exe as the parent of powershell.exe, pwsh.exe, cmd.exe, mshta.exe, wscript.exe, or rundll32.exe, especially with encoded commands, Invoke-WebRequest, curl, or writes to user-writable paths. Tie it back to a .lnk opened from Downloads, Temp, or an attachment cache followed within minutes by winget.exe configure.
Endpoint
T1204.002
T1059.001
T1218
T1105
Source: Winget DSC and Self-Referencing LNK File Attack Explained
#32
Jun 15, 2026
Hunt token replay that turns into Copilot data pulls
Hypothesis: An adversary reuses a stolen Microsoft 365 token, then uses Copilot or Azure AI to query SharePoint, OneDrive, or mailbox content and access the referenced files in the same window.
Why it matters: Microsoft published investigation guidance for reconstructing Copilot and Azure AI activity from identity, time, and resource context. That gives an MDR a concrete way to join token abuse to AI interactions and content access without guessing whether Copilot use is normal.
Starter hunt: Start in CloudTrail, DNS/HTTP logs, and identity sign-in logs. Pivot in Entra and M365 audit, find a session cookie or refresh token reused from two ASNs or countries inside an impossible-travel window. Require CopilotInteraction or Azure AI requests that reference SharePoint, OneDrive, or mail content, then FileAccessed, FileDownloaded, or send activity by the same user.
Identity
T1567
T1528
T1071.001
T1213
T1556.006
Source: Reconstructing AI activity in investigations