SCREEN_KILLER : Tool To Track Progress During Pentest Engagement & OSCP

SCREEN_KILLER script was to developed to capture screenshot during pentest engagment and OSCP.

IMPORTANT: The screenshot feature is no longer allowed for exam but the terminal logging is allowed for exam.

If you like the tool and for my personal motivation so as to develop other tools please a +1 star *

The tool can be used by pentesters, CTF players, students and trolls :).

**WARNING: SCREEN_KILLER is part of the KILLER project. SCREEN_KILLER is still under development and there might be some issues, please create an issue if you found any. **

Other tool will be added to the KILLER project in the coming months so stay tuned up. Also ideas, bug reports, contributions are more than welcome !

Overview

It is a tool that can to take screenshot for a self-defined period (seconds) and also to log all terminal commands.

This means that you can take track of all commands run for whatever number of terminals you have.

  • Important: The tool for now is dev for only bash terminal. Will not work on ZSH,CSH…for now (if interested drop an issue).

Features

Some of the functionalities

  • Automated screen capture
  • Commands logging

Usage

Requirement: scrot must be installed (apt-get install scrot). Remember to chmod +x all .sh for execute right.

./screen_killer.sh

It is recommended to run the tool as root but you can sudo ./screen_killer.sh .It should work but I have not tested all the features.

Then choose the feature that you want to run. It is important to stop the capturing at the end of the day.

Disclaimer

The usual disclaimer applies, especially the fact that me (TH3xACE) is not liable for any damages caused by direct or indirect use of the information or functionality provided by these programs. The author or any Internet provider bears NO responsibility for content or misuse of these programs or any derivatives thereof. By using these programs you accept the fact that any damage (dataloss, system crash, system compromise, etc.) caused by the use of the script is not my responsibility.

R K

Recent Posts

git fetch vs git pull: How They Work and When to Use Each

Both git fetch and git pull talk to a remote repository, but they do very different things to your…

5 days ago

git cherry-pick Command: Apply Commits from Another Branch

Sometimes the change you need already exists, just on the wrong branch. A hotfix lands…

5 days ago

Best Email APIs for Secure Business Email: Why Developers Are Moving Beyond SMTP

Email is still one of the most important communication channels inside modern applications. Password resets,…

6 days ago

Nginx Commands in Linux: Start, Stop, Reload, Test, and Log

Nginx is a high-performance web server and reverse proxy trusted by some of the largest…

1 week ago

ufw Command in Linux: Manage Firewall Rules with Examples

ufw (Uncomplicated Firewall) sits on top of iptables (or nftables on newer systems) and replaces…

1 week ago

who Command in Linux: Show All Logged-In Users and Sessions

When you share a server with a team or investigate unexpected activity, the first question…

1 week ago