Chkconfig Service Add
Detects the use of the chkconfig binary to manually add a service for management by chkconfig. Threat actors may utilize this technique to maintain persistence on a system. When a new service is added, chkconfig…
Description
Detects the use of the chkconfig binary to manually add a service for management by chkconfig. Threat actors may utilize this technique to maintain persistence on a system. When a new service is added, chkconfig ensures that the service has either a start or a kill entry in every runlevel and when the system is rebooted the service file added will run providing long-term persistence.
Detection logic
Its licence does not clear it for publishing here
Sunturai publishes a detection's own text where the licence it arrived under has been reviewed and permits it, and Elastic License 2.0 has not. The query as its source wrote it, its canonical form and the hash that pins this revision are in the workspace record.
Detection requirements
- Platform
- ContainersESXiLinuxmacOSNetwork DevicesWindows
The rule states no platform. This is derived from the 2 ATT&CK techniques it maps to.
- Log source category
- event_index
MITRE ATT&CK mappings
0 exclusive techniques.This is coverage no other published rule has; it is not this rule's total technique count.
References
| Reference | Cited by |
|---|---|
| www.intezer.com/blog/research/lightning-framework-new-linux-threat/ | 2 |
From the source
- At source
- Open at source
- Upstream identifier
- b910f25a-2d44-47f2-a873-aabdc0d355e6
- Tagged by the source as
- Data Source: Elastic DefendData Source: Elastic EndgameData Source: SentinelOneDomain: EndpointNoise: LowOS: LinuxPerformance: NormalPlatform: LinuxResources: Investigation GuideResources: OsqueryRule Type: Event Correlation (EQL)Tactic: PersistenceThreat: Lightning FrameworkUse Case: Threat Detection
Licence
- Published under
- Elastic License 2.0Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Sep 20, 2026
- Version
- 3