On this page

OSSEC / HIDS Rule 59335

OSSEC / HIDS rule catalog

  • Rule family: OSSEC / HIDS
  • Rule ID: 59335
  • Definition status: Present in current source
  • Alert message / subject: Windows: Code Integrity determined that the page hashes of an image file are not valid
  • Rule level: 6
  • Definition checked: 2026-10-21

Interpretation and response

This event is recorded as “Windows: Code Integrity determined that the page hashes of an image file are not valid”. Review the originating log and the affected host or service to determine whether the activity was expected.

An OSSEC/HIDS event records or correlates activity. Blocking depends on the originating application and any separately configured Active Response policy; an alert alone does not prove that an attack was blocked.

Documentation

The following guidance was migrated from the historical wiki and reviewed against the rule definition. Legacy ASL product names and interface instructions refer to the versions documented then. Use the current metadata above and your installed configuration when interpreting thresholds, notification settings and response behavior.

Description

Windows threat protection has indicated file could be improperly signed without page hashes or corrupt due to unauthorized modification. The invalid hashes could indicate a potential disk device error.

Code Integrity is a feature that improves the security of the operating system by validating the integrity of a driver or system file each time it is loaded into memory. Code Integrity detects whether an unsigned driver or system file is being loaded into the kernel, or whether a system file has been modified by malicious software that is being run by a user account with administrative permissions. On x64-based versions of the operating system, kernel-mode drivers must be digitally signed.

This event generates when code Integrity determined that the page hashes of an image file are not valid. The file could be improperly signed without page hashes or corrupt due to unauthorized modification. This event also generates when signing certificate was revoked. The invalid hashes could indicate a potential disk device error.

What you should do

Investigate this further, at the very least this could indicate a failing component. Malicious code masquerading as legitimate applications will also generate errors in this category.

Troubleshooting

False Positives

A legitimate event may still trigger this rule. Review the surrounding activity before deciding whether it is malicious.

Tuning Guidance

There is no guidance for tuning this rule, this is a Windows audit event and the rule should not be disabled.

Additional Information

Support

If you are unsure about how to respond to this alert, please contact Atomicorp support. We’re here to help you!

Source and revision

Migrated from HIDS_59335, wiki page 759, revision 6119 (20201021). Documentation review: 2026-10-21. An archived wiki status of Active is not a current deployment status.

For assistance, provide the rule ID, installed product and rule version, and a sanitized event to Atomicorp support .