HighCompromise indicatorsBLWK-PERSIST-004

Unexpected registry Run-key entry found

What this means

The registry Run-key entry “‹name›” launches “‹command›” on every login and isn't one this host's baseline recognizes — Windows's equivalent of a rogue systemd unit.

How to fix it

Review the entry under HKLM/HKCU ...\CurrentVersion\Run and remove it if you didn't create it.

Check it yourself

Run a scan and look for BLWK-PERSIST-004 in the results:

bulwark scan

Installed the standalone CLI package instead of the app? The command is bulwarkctl.

How Bulwark decides

Bulwark reads windows_run_keys and reports this check when:

recognized == false

If a value can't be read, Bulwark reports the check as undetermined rather than passing it. View the rule source.

References

• MITRE ATT&CK T1547.001

Related checks

• Shell history recording is suppressed · BLWK-EVASION-001
• File modified since baseline: ‹path› · BLWK-FIM-001
• File deleted since baseline: ‹path› · BLWK-FIM-002
• Not covered by the file-integrity baseline: ‹path› · BLWK-FIM-003
• Credential file modified since baseline: ‹path› · BLWK-FIM-004
• Credential file deleted since baseline: ‹path› · BLWK-FIM-005