Hacking on Medium
Can you explain the $100 million Mango hack to me?;

https://cdn-images-1.medium.com/max/1456/0*Y-ymgtlu2bL3jc0o.png
In this edition:

Continue reading on Medium »

___________________________
@hacking_Attack
@Hacking_Video

Hacking on Medium
Simple Python Ransomware

https://cdn-images-1.medium.com/max/1024/0*pgYV7udaqIgKaXbD
Link

Continue reading on Medium »

___________________________
@hacking_Attack
@Hacking_Video

Disappointment from interview.
https://www.reddit.com/r/Pentesting/comments/y7zb31/disappointment_from_interview/

Hello Redditors, Today I've gone through my first official Pen-testing ( Disappointment )interview. I am 32 years old and have been a system engineer/DevOps for a while now and I was looking to move into more offensive security fields. I've been studying web & network pen-testing for almost two years, did some bug bounties, HTB and THM & also did a couple of freelance web pen-testing. Took eWapt and eCCPT. The interview asked me to rate myself on the web, network, mobile pen-testing skills, and source code review. and I did rate as follows: Network --> 8/10. Web --> 6/10. Mobile --> 1/10 ( as I did not get there yet ). source code review --> 1/10 ​ By the end of the interview, he said that a focused offensive engineer shall have mastered all his Offensive skills 10 out of 10. And he told me that I am not focused enough, as I am shifting from one paradigm to another. ​ So I am disappointed and I started to doubt that I can get a position at such an age. What do you think? submitted by /u/morizk90 (https://www.reddit.com/user/morizk90)
[link] (https://www.reddit.com/r/Pentesting/comments/y7zb31/disappointment_from_interview/) [comments] (https://www.reddit.com/r/Pentesting/comments/y7zb31/disappointment_from_interview/)

___________________________
@hacking_Attack
@Hacking_Video

PenguinTrace - Tool To Show How Code Runs At The Hardware Level
http://www.kitploit.com/2022/10/penguintrace-tool-to-show-how-code-runs.html

___________________________
@hacking_Attack
@Hacking_Video

penguinTrace (https://penguintrace.org/) is intended to help build an understanding of how programs run at the hardware level. It provides a way to see what instructions compile to, and then step through those instructions and see how they affect machine state as well as how this maps back to variables in the original program. A bit more background (https://penguintrace.org/2019/04/29/welcome-and-background.html) is available on the website. penguinTrace starts a web-server which provides a web interface to edit and run code. Code can be developed in C, C++ or Assembly. The resulting assembly is then displayed and can then be stepped through, with the values of hardware registers and variables in the current scope shown. penguinTrace runs on Linux and supports the AMD64/X86-64 and AArch64 architectures. penguinTrace can run on other operating systems using Docker, a virtual machine (https://www.kitploit.com/search/label/Virtual%20Machine) or through the Windows Subsystem for Linux (WSL).
The primary goal of penguinTrace is to allow exploring how programs execute on a processor, however the development provided an opportunity to explore how debuggers work and some lower-level details of interaction with the kernel. Note: penguinTrace allows running arbitrary code as part of its design. By default it will only listen for connections from the local machine. It should only be configured to listen for remote connections on a trusted network and not exposed to the interface. This can be mitigated by running penguinTrace in a container, and a limited degree of isolation of stepped code can be provided when libcap is available. Getting Started Prerequisites penguinTrace requires 64-bit Linux running on a X86-64 or AArch64 processor. It can also run on a Raspberry Pi (https://www.kitploit.com/search/label/Raspberry%20Pi) running a 64-bit (AArch64) Linux distribution. For other operating systems, it can be run on Windows 10 (https://www.kitploit.com/search/label/Windows%2010) using the Windows Subsystem for Linux (WSL) or in a Docker container. WSL does not support tracee process isolation. python
clang
llvm
llvm-dev
libclang-dev
libcap-dev # For containment
Building To build penguinTrace outside of a container, clone the repository and run make. The binaries will be placed in build/bin by default. To build penguinTrace in Docker, run docker build -t penguintrace github.com/penguintrace/penguintrace. Running Once penguinTrace is built, running the penguintrace binary will start the server. If built in a container (https://www.kitploit.com/search/label/Container) it can then be run with docker run -it -p 127.0.0.1:8080:8080 --tmpfs /tmp:exec --cap-add=SYS_PTRACE --cap-add=SYS_ADMIN --rm --security-opt apparmor=unconfined penguintrace penguintrace. See Containers (https://github.com/penguintrace/penguintrace#containers) for details on better isolating the container. Then navigate to 127.0.0.1:8080 (http://127.0.0.1:8080/) or localhost:8080 (http://localhost:8080/) to access the web interface. Note: In order to run on port 80, you can modify the docker run command to map from port 8080 to port 80, e.g. -p 127.0.0.1:80:8080. If built locally, you can modify the binary to allow it to bind to port 80 with sudo setcap CAP_NET_BIND_SERVICE=+ep penguintrace. It can then be run with penguintrace -c SERVER_PORT 80 penguinTrace defaults to port 8080 as it is intended to be run as an unprivileged user. Temporary Files The penguinTrace server uses the system temporary directory as a location for compiled binaries and environments for running traced processes. If the PENGUINTRACE_TMPDIR environment variable is defined, this directory will be used. It will fall back to the TMPDIR environment variable and finally the directories specified in the C library. This must correspond to a directory without noexec set, if running in a container it is likely the filesystem (https://www.kitploit.com/search/label/Filesystem) will

___________________________
@hacking_Attack
@Hacking_Video

have this set by default. Networking By default penguinTrace only listens on the loopback device and IPv4. If the server is configured to listen on all addresses, then also setting the server to IPv6 will allow connections on both IPv4 and IPv6, this is the default mode when running in a Docker container. This is because penguinTrace only creates a single thread to listen to connections and so can currently only bind to a single address or all addresses. Session Handling By default penguinTrace runs in multiple session mode, each time code is compiled a new session is created. The URL fragment (after the '#') of the UI is updated with the session id, and this URL can be used to reconnect to the same session. If running in single session mode each penguinTrace instance only supports a single debugging instance. The web UI will automatically reconnect to a previous session. To support multiple sessions, multiple instances should be launched which are listening on different ports. Containers The docker_build.sh and docker_run.sh scripts provide an example of how to run penguinTrace in a Docker container. Dockerfile_noisolate provides an alterative way of running that does not require the SYS_ADMIN capability but provides less isolation between the server and the traced processes. The SYS_PTRACE capability is always required for the server to trace processes. misc/apparmor-profile provides an example AppArmor profile that is suitable for running penguinTrace but may need some customisation for the location of temporary directories and compilers. AArch64 / Raspberry Pi penguinTrace will only run under a 64-bit operating system. The official operating systems provided for the Raspberry Pi are all 32-bit, to run penguinTrace something such as pi64 (https://github.com/bamarni/pi64) or Arch Linux Arm (https://archlinuxarm.org/platforms/armv8/broadcom/raspberry-pi-3) is required. Full instructions for setting up a 64-bit OS on Raspberry Pi TBD. Authors penguinTrace is developed by Alex Beharrell (https://github.com/martiansoup). License This project is licensed under the GNU AGPL. A non-permissive open source license is chosen as the intention of this project is educational, and so any derivative works should have the source available so that people can learn from it. The bundling of the source code relies on the structure of the repository. Derivative works that are not forked from a penguinTrace repository will need to modify the Makefile rules for static/source.tar.gz to ensure the modified source is correctly distributed. Acknowledgements penguinTrace makes use of jQuery (https://jquery.com/) and CodeMirror (https://codemirror.net/) for some aspects of the web interface. Both are licensed under the MIT License. It also uses the Major Mono (http://www.emreparlak.com/major/) font which is licensed under the Open Font License.

Download Penguintrace (https://github.com/penguintrace/penguintrace)

___________________________
@hacking_Attack
@Hacking_Video

hacking: security in practice
Responder

Hi all,

Quick question regarding the tool “Responder”, did any of you had any success using responder during internal client investigations (capturing NTLMv2 hashes). I used it a few times without any captured hashes..

Thanks in advance!

submitted by /u/_maxk
[link] [comments]

___________________________
@hacking_Attack
@Hacking_Video

hacking: security in practice
Is there a way to automatically decompress a compressed file using an exe file

I’m trying to create a zip bomb which can be automatically decompressed without user input, i understand how to create the bomb just not how to effectively deliver it.

submitted by /u/CenturionB27Q
[link] [comments]

___________________________
@hacking_Attack
@Hacking_Video

hacking: security in practice
Im just starting out and im pretty overwhelmed.

I dont know should i go through pentesting path or the attacker path or defensive path ? Which one of these paths come in handy in ctf since i wanna try it as soon as i learn the basics, last thing is is tryhackme.com good for learning ?

submitted by /u/IX7L
[link] [comments]

___________________________
@hacking_Attack
@Hacking_Video

hacking: security in practice
Opinions to protonmail

What do you think about protonmail? Is the data (relatively) safe?

submitted by /u/altanerf
[link] [comments]

___________________________
@hacking_Attack
@Hacking_Video

hacking: security in practice
Sorillus The Rat

So there is a rat called Sorillus, you can look at up on youtube if your unfamiliar, but my query is with those who may ne familiar. Im just curious of an experiences with this client, if its good, or preferred to others. What rat do you think is the best? This is all in the name of friendly conversation, and educational purposes.

submitted by /u/ChimpionYT
[link] [comments]

___________________________
@hacking_Attack
@Hacking_Video

KitPloit - PenTest Tools!
PenguinTrace - Tool To Show How Code Runs At The Hardware Level

https://blogger.googleusercontent.com/img/a/AVvXsEgt4I-nU8mfkEt4Ej4-4EJHArZpyZCwTNveUanbGLF8lOYNnjEqNeyCH2aw4QECwjNQkpl8-5Zhwi2mQPUm2Q5Z4Bpu-ai308ZBW_x0XaZlOiNP3CU-USNLHmkmJckefdcw8EDmtADuTejgE2OQbNl9j8AJ8vLNLP1rfW8MR8GztX9YN5Ao-F58ChoI8Q=w640-h346 penguinTrace is intended to help build an understanding of how programs run at the hardware level. It provides a way to see what instructions compile to, and then step through those instructions and see how they affect machine state as well as how this maps back to variables in the original program. A bit more background is available on the website.

penguinTrace starts a web-server which provides a web interface to edit and run code. Code can be developed in C, C++ or Assembly. The resulting assembly is then displayed and can then be stepped through, with the values of hardware registers and variables in the current scope shown.

penguinTrace runs on Linux and supports the AMD64/X86-64 and AArch64 architectures. penguinTrace can run on other operating systems using Docker, a virtual machine or through the Windows Subsystem for Linux (WSL).
The primary goal of penguinTrace is to allow exploring how programs execute on a processor, however the development provided an opportunity to explore how debuggers work and some lower-level details of interaction with the kernel.

Note: penguinTrace allows running arbitrary code as part of its design. By default it will only listen for connections from the local machine. It should only be configured to listen for remote connections on a trusted network and not exposed to the interface. This can be mitigated by running penguinTrace in a container, and a limited degree of isolation of stepped code can be provided when libcapis available. Getting StartedPrerequisitespenguinTrace requires 64-bit Linux running on a X86-64 or AArch64 processor. It can also run on a Raspberry Pi running a 64-bit (AArch64) Linux distribution. For other operating systems, it can be run on Windows 10 using the Windows Subsystem for Linux (WSL) or in a Docker container. WSL does not support tracee process isolation. python
clang
llvm
llvm-dev
libclang-dev
libcap-dev # For containment BuildingTo build penguinTrace outside of a container, clone the repository and run make. The binaries will be placed in build/binby default.

To build penguinTrace in Docker, run docker build -t penguintrace github.com/penguintrace/penguintrace. RunningOnce penguinTrace is built, running the penguintracebinary will start the server.

If built in a container it can then be run with docker run -it -p 127.0.0.1:8080:8080 --tmpfs /tmp:exec --cap-add=SYS_PTRACE --cap-add=SYS_ADMIN --rm --security-opt apparmor=unconfined penguintrace penguintrace. See Containers for details on better isolating the container.

Then navigate to 127.0.0.1:8080 or localhost:8080 to access the web interface.

Note: In order to run on port 80, you can modify the docker runcommand to map from port 8080 to port 80, e.g. -p 127.0.0.1:80:8080.

If built locally, you can modify the binary to allow it to bind to port 80 with sudo setcap CAP_NET_BIND_SERVICE=+ep penguintrace. It can then be run with penguintrace -c SERVER_PORT 80penguinTrace defaults to port 8080 as it is intended to be run as an unprivileged user. Temporary FilesThe penguinTrace server uses the system temporary directory as a location for compiled binaries and environments for running traced processes. If the PENGUINTRACE_TMPDIRenvironment variable is defined, this directory will be used. It will fall back to the TMPDIRenvironment variable and finally the directories specified in the C library.

Th[...]

___________________________
@hacking_Attack
@Hacking_Video

is must correspond to a directory without noexecset, if running in a container it is likely the filesystem will have this set by default. NetworkingBy default penguinTrace only listens on the loopback device and IPv4. If the server is configured to listen on all addresses, then also setting the server to IPv6 will allow connections on both IPv4 and IPv6, this is the default mode when running in a Docker container.

This is because penguinTrace only creates a single thread to listen to connections and so can currently only bind to a single address or all addresses. Session HandlingBy default penguinTrace runs in multiple session mode, each time code is compiled a new session is created. The URL fragment (after the '#') of the UI is updated with the session id, and this URL can be used to reconnect to the same session.

If running in single session mode each penguinTrace instance only supports a single debugging instance. The web UI will automatically reconnect to a previous session. To support multiple sessions, multiple instances should be launched which are listening on different ports. ContainersThe docker_build.shand docker_run.shscripts provide an example of how to run penguinTrace in a Docker container. Dockerfile_noisolateprovides an alterative way of running that does not require the SYS_ADMINcapability but provides less isolation between the server and the traced processes. The SYS_PTRACEcapability is always required for the server to trace processes. misc/apparmor-profileprovides an example AppArmor profile that is suitable for running penguinTrace but may need some customisation for the location of temporary directories and compilers. AArch64 / Raspberry PipenguinTrace will only run under a 64-bit operating system. The official operating systems provided for the Raspberry Pi are all 32-bit, to run penguinTrace something such as pi64 or Arch Linux Arm is required.

Full instructions for setting up a 64-bit OS on Raspberry Pi TBD. AuthorspenguinTrace is developed by Alex Beharrell. LicenseThis project is licensed under the GNU AGPL. A non-permissive open source license is chosen as the intention of this project is educational, and so any derivative works should have the source available so that people can learn from it.

The bundling of the source code relies on the structure of the repository. Derivative works that are not forked from a penguinTrace repository will need to modify the Makefile rules for static/source.tar.gzto ensure the modified source is correctly distributed. AcknowledgementspenguinTrace makes use of jQuery and CodeMirror for some aspects of the web interface. Both are licensed under the MIT License. It also uses the Major Mono font which is licensed under the Open Font License. Download Penguintrace

___________________________
@hacking_Attack
@Hacking_Video

Hacking on Medium
Kali Linux — The Paradise for Hackers ! | All About Kali Linux !

Kali Linux is a Debian-derived Linux distribution designed for digital forensics and penetration testing. It is maintained and funded by…

Continue reading on Medium »

___________________________
@hacking_Attack
@Hacking_Video

Hacking on Medium
Do you want to network with IT and Cyber Security Experts?

https://cdn-images-1.medium.com/max/1970/1*MPyqIg5DpXoDQ-Remxw6Rw.jpeg
LOGYTalks, the new innovative conference platform, is hosting the first of its annual Cyber Security Summits on Thursday 27th October 2022…

Continue reading on Medium »

___________________________
@hacking_Attack
@Hacking_Video

Hacking on Medium
How to set up Virtual-Boxes and Kali Linux for Hacking?

https://cdn-images-1.medium.com/max/2600/0*IWNzRhQB4dxxuS8y
Setting Up Your Boxes

Continue reading on Medium »

___________________________
@hacking_Attack
@Hacking_Video