Security

Third-Party Compromise Enables Stealthy Trusted Access

3 min read

Summary

Microsoft Incident Response detailed a stealthy intrusion in which attackers abused a compromised third-party IT services provider and trusted management tools to gain long-term access. The case highlights how legitimate admin channels, identity infrastructure, and web-based persistence can be misused, making stronger monitoring of trusted relationships critical for defenders.

Need help with Security?Talk to an Expert

Introduction

Microsoft has published a new incident response case study showing how threat actors can bypass traditional detection by abusing trusted relationships instead of relying on obvious malware or exploits. For IT and security teams, the key takeaway is clear: approved tools, delegated admin models, and third-party service providers can become part of the attack surface.

What happened

Microsoft Incident Response investigated an intrusion where the attacker compromised a third-party IT services provider and used legitimate enterprise management tooling to operate inside the customer environment.

Key findings

  • The attacker used HPE Operations Agent (OA) and HPE Operations Manager (HPOM) as the primary delivery path.
  • Microsoft noted there was no vulnerability in HPE OA itself; the risk came from abuse of a trusted operational relationship.
  • Activity blended in with normal administration, delaying detection.
  • The campaign focused on:
    • Long-term persistence
    • Credential theft
    • Lateral movement
    • Reestablishing access after partial disruption

Attack progression

Microsoft’s timeline shows a slow, deliberate intrusion:

  • Day 1: Initial foothold through the third-party trust path
  • Days 9–14: Credential interception introduced on domain infrastructure
  • Days 24–32: Web-based persistence established on internet-facing servers
  • Days 40–60: Lateral movement to additional and sensitive systems
  • Days 104–106: Persistence reestablished after detection efforts

Techniques used

The report highlights several notable methods:

  • Web shells found on internet-exposed web servers
  • VBScript deployment through HPOM to execute discovery actions
  • Credential harvesting on domain controllers using a malicious network provider named mslogon
  • Abuse of Windows authentication notification APIs such as:
    • NPLogonNotify
    • NPPasswordChangeNotify

This allowed the attacker to capture cleartext credentials during sign-ins and password changes, then store them locally for reuse.

Why this matters for administrators

This incident is a strong reminder that security monitoring cannot focus only on malware, exploits, or unknown binaries. Legitimate signed tools and delegated administration platforms can be used as attack infrastructure when trust boundaries are not tightly controlled.

Security teams should pay particular attention to:

  • Third-party remote management and monitoring platforms
  • Administrative script execution through approved tools
  • Unexpected changes to network providers on domain systems
  • Authentication-related DLL registrations and credential access behavior
  • Persistence mechanisms on internet-facing servers

Microsoft’s post includes Defender detection and hunting guidance, along with mitigation recommendations. Organizations should:

  • Review and restrict third-party privileged access
  • Audit trust relationships and delegated admin paths
  • Hunt for unusual HPOM/HPE OA-driven script execution
  • Monitor domain controllers for unauthorized network provider registration
  • Validate persistence checks on web servers and sensitive assets

The broader lesson is simple: trusted relationships must be monitored as closely as untrusted ones.

Need help with Security?

Our experts can help you implement and optimize your Microsoft solutions.

Talk to an Expert

Stay updated on Microsoft technologies

Securitythird-party compromisetrusted relationshipcredential theftMicrosoft Defender

Related Posts

Security

Microsoft Sentinel Named a 2026 SIEM Leader

Microsoft has been named a Leader in the 2026 Gartner Magic Quadrant for SIEM, highlighting the continued momentum behind Microsoft Sentinel. The announcement also underscores Microsoft's push toward integrated, AI-powered security operations through deep Sentinel integration with the new Integrated Security Operations Center in Microsoft Defender.

Security

Microsoft Perception GA: Agentic Security at Ignite

Microsoft has made Microsoft Perception generally available, introducing an agentic security platform that coordinates red, blue, and green team agents through automated playbooks. Announced at Ignite 2026, the update also expands Defender and Sentinel capabilities to help security teams detect, investigate, and remediate AI-speed threats while keeping administrators in control.

Security

Device Code Phishing Risks for AI Coding Agents

Microsoft warns that device code phishing can be used against AI coding agents such as GitHub Copilot CLI, not just user mailboxes or cloud apps. In a controlled lab, a single approved device code sign-in could enable remote session steering, memory poisoning, synced session exposure, and private repository access depending on account permissions and enabled features.

Security

Microsoft 365 Outage Phishing Campaign Targets Users

Microsoft Threat Intelligence reported a high-volume phishing campaign that impersonates Microsoft 365 service-health notifications to trick users into clicking malicious links. The campaign matters because it uses outage-themed urgency and recipient-specific tracking to target multiple industries, increasing the risk of credential theft and follow-on account compromise.

Security

SCKit ScreenConnect Attack: MSPs Must Hunt Now

Microsoft Threat Intelligence confirmed a campaign abusing ConnectWise ScreenConnect to deploy unauthorized remote-access clients and the SCKit worm on MSP-managed endpoints. The activity can also target technician sessions, making this a high-priority incident for defenders because removing a rogue client alone does not eliminate persistence or invalidate exposed sessions.

Security

AI Agent Supply Chain Attacks Target Coding Tools

Microsoft Security researchers detailed two post-training supply chain attack paths that can backdoor coding and terminal agents: dataset poisoning and model poisoning. The findings matter because compromised agents can misuse tools, execute commands, and access sensitive environments even when prompts appear benign, reinforcing the need for stronger controls around training data, model provenance, and tool permissions.