Guide

Check Word and Excel files for macro signals

Inspect unexpected Word, Excel and PowerPoint files for macro containers and external relationships before opening. ScanBeforeOpen examines supported OOXML packages locally without running macros.

Responsible operator: Tom Silas Helmke, operator of ScanBeforeOpen. Content revised: .

Open scanner

What local macro inspection detects

Extensions such as .docm, .xlsm and .pptm, along with vbaProject.bin inside a supported ZIP package, are important signals. External template relationships, data connections, OLE/ActiveX content and embedded objects can produce further findings.

Inspection examines names and selected XML patterns. It neither executes nor decompiles VBA, and does not establish benign content or the complete absence of active structures.

How a macro sits in an Office file
Macro enabled file.docm, .xlsm, .pptmPackage part vbaProject.binstored VBA codeOpening in Officemacros are blocked at firstEnable contentonly then can macros runScanBeforeOpendetects extension and vbaProject.bin

The sequence in words

  1. Files such as .docx, .xlsx and .pptx cannot store macros. Macros appear only in macro enabled formats such as .docm, .xlsm and .pptm.
  2. Inside the ZIP package the code sits as the part vbaProject.bin. The mere presence of this part is a clear signal.
  3. According to Microsoft, Office blocks macros in files from the internet by default. The file first opens without running code.
  4. Only when someone enables content or macros can the code run. Enable that only for sources you trust.
  5. The scanner reads the package structure, reports the extension and vbaProject.bin and never executes a macro. It does not assess the code.

Comments, hidden sheets and text excerpts

docProps, customXml, comments and hidden worksheets can hold private or nonvisible information. Preview is a limited extracted text excerpt, not a faithful workbook.

Hidden or commented content can appear in that excerpt. Other parts can be missing. Do not infer complete visibility, cell mapping or removal of confidential information.

After a macro finding

Do not enable macros or external content just to dismiss a warning. Confirm unexpected documents through a separate channel and involve the responsible IT team. A trusted source alone does not establish technical safety.

Legacy binary Office formats and password-protected files may have no supported content inspection. An unexpected extension or damaged package is a reason to read coverage closely.

Why there is no cleaned Office download

Experimental OOXML cleaning and Visible Data Rebuild are disabled. Simply deleting macro files can break references or leave active structures behind.

The inspection report is available; suitable documents may offer limited text excerpts. These are neither cleaned DOCX/XLSX/PPTX files nor complete tables.

Practical checklist

  • Keep unexpected documents closed and confirm their source
  • Assess extensions together with OOXML structural signals
  • Do not enable macros or external data just because a document asks
  • Do not treat a text excerpt as a complete workbook
  • Respect the deliberate Office export block

Clear limits

Limited OOXML inspection within ZIP budgets. No complete VBA, binary-format or document-semantics analysis, and no Office reconstruction.

FAQ

Can ScanBeforeOpen remove macros from Excel files?

No. Office cleaning and Visible Data Rebuild are blocked. The scanner provides limited signals, not a validated cleaned Office document.

Is an XLSX safe without a macro finding?

No. External relationships, active embedded objects and unsupported structures can matter independently. There is no malware clearance.

Is Office preview complete and visible-only?

No. It is a limited text excerpt and can contain hidden content or comments. Complete cell or visibility reconstruction does not take place.

Related reading

Technical sources