Repository navigation
Releases
Releases · Bl4ckk01/checkBackdoor
CheckBackdoor 1.4.0
1.4.0
Added
- More actions on findings in the app: Quarantine suspicious files, Remove
extension from the browser (the browser must be closed), Remove exclusion from
Defender, Disable account, Remove certificate (all with a backup and Undo), and
End process for suspicious processes. - Delete for suspicious files and browser extensions: deletes them for good, after a
warning about false positives. It refuses a file that changed after the scan. - Backup page in the app bar, shown only while something is in quarantine: every file
and browser extension moved away, with Restore and Delete for good. Deleting never
follows a link out of the backup folder.
Changed
- "Show the file" also works on items that are folders (browser extensions), and is called
"Show the folder" for them. - Fix all, at the top right of the results: fixes every high and medium-risk item that
has an action, with one confirmation (the full list and a warning) and one Windows prompt.
Files are deleted, everything else disabled. Its number goes down as items are fixed.
Fixed
- The timeline reported CheckBackdoor's own modules as suspicious PowerShell scripts: Windows
logs them (event 4104) and the text read from the log has different line endings from the
files, so the engine no longer recognized them as its own.
CheckBackdoor 1.3.0
1.3.0
The first public release.
Changed
- Everything is in English: interface, report, messages, code, comments and docs. File
names changed accordingly:Start-Scan.bat,Check-File.bat,Actions.ps1,
tools\Test-Detections.ps1, reportsscan_*andcheck_*, app dataignored.jsonand
settings.json, scheduled task\CheckBackdoor\Weekly scan. Severities areHigh,
Medium,LowandInfo. Reports from earlier versions are not shown in the app history. - Command-line analysis moved from
Common.ps1to its own module,CommandRisk.ps1.
Fixed
- The report subtitle glued the date and the Windows version together without a separator.
Security
- Install to Program Files (administrator needed): the engine runs as administrator, so it
must not live in a folder a user program can change. PowerShell is started by its full path. - Protected backups: changes made as administrator save their backup in
%ProgramData%\CheckBackdoor\backup, writable only by administrators, and "Undo" with those
rights restores only backups from that folder. A moved file goes back only if its SHA-256
hash is the one saved. - "Disable" shows the item that will really be changed, does not touch the services of the
installed antivirus and rejects a request changed after the confirmation (-RequestSha256). - Allowlist: rules that are too broad (
*,*.exe, whole user or system folders) are not
applied and are flagged; an item ignored from the app shows up again if the file changes; the
report lists everything the allowlist hid, with the rule. - Content-Security-Policy in the report and the interface: only CheckBackdoor scripts run.
- Release: GitHub actions pinned to a commit and provenance attestation of the files.