Malicious TELEPUZ Service Persistence via CipherAllocator Registry Key

ATT&CK techniques

Persistence → Priv Esc

Recon
Resource Dev
Initial Access
Execution
Persistence
- T1543.003Windows Service
Priv Esc
- T1543.003Windows Service
Defense Evasion
Cred Access
Discovery
Lateral Movement
Collection
C2
Exfiltration
Impact

What it detects

This rule detects creation of the CipherAllocator service registry key which TELEPUZ registers for privileged persistence after loading its DLL payload. Naming a malicious service to resemble a legitimate cryptographic component helps it hide among system services. This fixed service name is a high-confidence indicator of the MaaS foothold.

Reporting behind it

Related detections9 linkedT1543.003 — drag to rearrange

Malicious Service Created With Binary Path in ProgramData

Malicious Abyss Locker wmihelper SSH Backdoor Deployment (via file_event)

Malicious AuKill EDR Killer Kernel Driver Load via Process Explorer Driver (via image_load)

Suspicious TermService ServiceDll Hijack via Registry (via registry_set)

Suspicious Service Creation Named RDP-Controller via sc.exe (via process_creation)

Suspicious Service or Task Named windowsinspectionupdate (via process_creation)

Malicious Service Persistence via sc.exe Creating msdnetsvc

Suspicious Stately Taurus Masqueraded Service and Task Persistence via process_creation

Malicious Vulnerable Driver Load for EDR Evasion (via image_load)

Malicious TELEPUZ Service Persistence via CipherAllocator Registry Key

Pivot detection · T1543.003 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.

Full detection rule

Unlock this rule to view and copy it

The detection logic is included with a plan. Everything else — context, mappings and implementation details — stays free on this page.

Sign in for 3 free unlocks

Signing in gives you 3 unlocks to spend on any rule in the library. No card, and they do not expire.

Also included

Unlocked rules convert on this page — to Splunk SPL or Splunk — Raw Index SPL or Microsoft Sentinel KQL or Microsoft Sentinel ASIM ASIM KQL or Microsoft Defender XDR KQL or Elastic Security KQL or Elastic Security Lucene or Elastic Security ES|QL or CrowdStrike Falcon CQL or SentinelOne PowerQuery or Palo Alto Cortex XDR XQL or Carbon Black Cloud Platform Search or Carbon Black EDR Process Search or Google Security Operations UDM Search or IBM QRadar AQL or Sumo Logic Cloud SIEM Rules expression or Rapid7 InsightIDR LEQL or Graylog Search or OpenSearch Lucene or OpenSearch PPL PPL or Grafana Loki LogQL or SQLite SQL or Zircolite SQLite — with the log-source profile the engine picked, the field map it used, and everything it could not express. Converting a rule you have unlocked costs no further credit.

See it run on a free rule →Convert your own rule →