Skip to main content

000

000 Permission Code:

Use 000 only as a quarantine and investigation tool, never as a normal WP file permission.

Summary:

NoStatementStatus
1000 removes all access for everyone✅
2Useful for isolating malware or suspicious files✅
3Root can still override✅
4Never use on core WP files or directories✅
5This is a forensic & security containment tool✅

Key Takeaways​

  1. Restore after testing

    chmod 644 test.php

  2. Confirm access denied

  3. Set to 000

    chmod 000 test.php

  4. Copy a harmless test file

Practice Exercise (Safe Only)​

NoIssueFix
1Locked file cannot be openedbecome root or restore perms
2Plugin broken after applyingrevert permissions
3Can't delete fileroot remove only

Troubleshooting​

chmod 644 filename

Restore normal state​

Access: (0000/----------)

Expected:

stat filename

Verify​

chmod 000 filename

Apply lockdown​

Commands​

Use **only on isolated files during emergency or investigation.

NoFile/DirResultAllowed?
1wp-config.phpsite fatal error❌
2wp-content/site fails to load content❌
3plugin/theme fileWP fatal error❌
4.htaccess or server configrouting breaks❌
5uploads foldermedia inaccessible❌

Situations Where 000 Will Break WordPress​

  • Want to prevent execution before deleting
  • Backdoor found after plugin/theme exploit
  • Unknown file discovered in /wp-content/uploads/ or /tmp
  • Malware detected but you want forensic evidence intact
  • WordPress site suspected of compromise

Scenarios Where 000 is Useful​

rm suspicious.php

or remove:

chmod 644 suspicious.php

Restore after analysis (if safe)​

sudo cat suspicious.php

Investigate safely afterward (root only)​

chmod -R 000 wp-content/uploads/.tmp/

Freeze an entire malicious folder​

chmod 000 suspicious.php

Quarantine a suspicious script​

Typical Security Operations​

NoUse CaseSuitableReason
1Malware quarantine✅isolate active malicious file
2Suspicious PHP backdoor✅neutralize without deleting yet
3Lock unknown script during audit✅prevents execution & viewing
4Secure forensic investigation✅preserve evidence
5Normal WP operations❌breaks functionality
6WP core, themes, plugins, uploads❌site will fail

WordPress Use Cases​

Only root can override this state.

  • File becomes completely inaccessible and inert
  • No one can modify or delete (unless via root)
  • No one can execute the file
  • No one can read the file

Behavior​

NoRoleBitsAccessAllowed?
1Owner---no access✅
2Group---no access✅
3Others---no access✅

Technical Structure​

It is a **special-purpose, emergency, or isolation permission used only when you want to quarantine files or freeze access entirely.

This mode is almost never used in normal WordPress operations.

---------

000 removes **all permissions from a file or directory: no read, no write, no execute for owner, group, or others.

Permission Code: 000 No Access for Anyone (Quarantine Mode)