DE

↑ ↓ select, Enter open, Esc close

Detect modified files of installed packages

harmless rootSecuritydebian, ubuntu
root@server
dpkg --verify

Compares the MD5 checksums of all files of installed packages with the values from the package database. Only deviations are printed: a 5 in the third position means changed content, a c marks configuration files. Changed configuration files are normal, changed programs under /usr/bin or /usr/sbin are not.

Note: The checksums are stored on the same system and could also have been modified by an attacker with root privileges. The run takes a few minutes.

Also searched as

  • verify package files debian
  • check system binaries for tampering
  • dpkg verify rootkit check

Related one-liners

All in Security

Find recently modified PHP files

$find /var/www/vhosts/example.com/httpdocs -type f -name '*.php' -mtime -7 -printf '%TY-%Tm-%Td %TH:%TM %p\n' | sort -r
harmlessSecurity

Find files modified between two dates

$find /var/www/vhosts/example.com/httpdocs -type f -newermt '2026-10-01' ! -newermt '2026-10-08' -printf '%TY-%Tm-%Td %TH:%TM %p\n' | sort
harmlessFilesystem

Find files modified in the last minutes

$find /var/www/vhosts/example.com/httpdocs -type f -mmin -60 -printf '%TY-%Tm-%Td %TH:%TM %p\n' | sort -r
harmlessFilesystem

Find which installed package a file belongs to

$dpkg -S /usr/bin/curl
harmlessDebian and APT

Fix an interrupted installation and broken dependencies

#dpkg --configure -a && apt --fix-broken install
cautionDebian and APT

Show all timestamps and permissions of a file

$stat /var/www/vhosts/example.com/httpdocs/wp-config.php
harmlessFilesystem

Read first, then run.

The commands on myline.de act directly on servers, files and databases. A wrong path or placeholder can delete data irreversibly or make a server unreachable.

  • All commands are provided without warranty and are not tested on every system.
  • Understand what a command does before running it, and check every placeholder.
  • Make a backup first and, if possible, try it on a test system.
  • You run commands at your own risk. Liability for damages is excluded to the extent permitted by law.