โ† Back to canonical report

Hunt

ShinyHunters Targets Education Sector with Oracle PeopleSoft Exploit

Hunt Strategy & Objective

Identify unauthenticated access to Oracle PeopleSoft EMHub endpoints and subsequent MeshCentral agent deployment.

โฑ๏ธ Lookback: 30 days

Hunt Hypothesis

Threat actors exploited CVE-2026-35273 via /PSEMHUB/hub to stage MeshCentral agents and execute fanout credential spraying scripts.

Target Platforms & Environment

Linux Windows

All internet-facing and internal Oracle PeopleSoft application servers running WebLogic and Process Scheduler.

Required Telemetry & Data Sources

Web server access logs Process execution logs Outbound NetFlow/firewall logs

โœ“ Operational Execution Phases

2 Structured Investigation Phases
1

Web Tier Perimeter Audit

Web server access logs

๐ŸŽฏ Phase Goal: Identify initial unauthenticated exploit attempts against PeopleSoft EMHub endpoints.

Procedural Actions

  1. 1.1 Filter web access logs for HTTP POST requests to /PSEMHUB/hub and /PSIGW/HttpListeningConnector.
  2. 1.2 Isolate source IPs outside of the trusted administrative range and correlate with subsequent 200 OK responses.

Phase Hunting Logic & Queries

spl EMHub Perimeter POST Requests
index=web (uri_path="/PSEMHUB/hub*" OR uri_path="/PSIGW/HttpListeningConnector*") http_method=POST | stats count by src_ip, status
๐Ÿ’ก Tuning & Baselines: Filter out internal node status probes

Anomaly Confirmation & Pivot Guidance

โ†ช Pivot from external source IPs to all subsequent web requests across the DMZ fleet.

2

Host Execution & Persistence Inspection

Process execution logs File integrity logs

๐ŸŽฏ Phase Goal: Determine whether MeshCentral agents or unauthorized webshells were written to disk and executed.

Procedural Actions

  1. 2.1 Examine file creation telemetry under /PSEMHUB.war/ and temp staging folders.
  2. 2.2 Verify running processes for meshagent, meshctrl.js, or unexpected node instances.

Phase Hunting Logic & Queries

spl MeshAgent Execution Events
index=endpoint (process_name="meshagent*" OR process_name="meshctrl.js") | table _time, host, user, process_path
๐Ÿ’ก Tuning & Baselines: Confirm if remote management tools are authorized in your environment

Anomaly Confirmation & Pivot Guidance

โ†ช Inspect local user accounts and cron / systemd units created around the execution timestamp.

โœ“

True Positive Confirmation Evidence

โ— POST requests to /PSEMHUB/hub with HTTP 200 responses
โ— Execution of meshagent from /tmp or staging directories
โ— Extortion marker files in WebLogic docroot
!

Benign & False Positive Explanations

โ— Authorized administrative Environment Management Hub traffic between verified PeopleSoft nodes.

๐Ÿ”ฌ Forensic Artifacts to Collect & Preserve

WebLogic access.log
/tmp/*fanout.sh
README-IF-YOU-SEE-THIS-YOUVE-BEEN-HACKED.TXT

Validation Checklist

Verify timestamp alignment between web access log POST and local process spawning.
Confirm whether meshagent persistence was established in systemd or Windows Services.

Escalation Criteria

Confirmation of unauthorized JSP file written to PSEMHUB.war or outbound data transfer to known DLS IP 176.120.22.24.

Traceability & Related Detections

๐Ÿ” Evidence: b9525252-2eโ€ฆ ๐Ÿ” Evidence: e658c69d-2cโ€ฆ ๐Ÿ” Evidence: 70c65482-8dโ€ฆ ๐Ÿ›ก๏ธ Detection: 485b5bec-5bโ€ฆ ๐Ÿ›ก๏ธ Detection: 579a4353-ddโ€ฆ