# evilsocket I hack stuff. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Mongoose: Preauth RCE and mTLS Bypass on Millions of Devices DevFeed: [Mongoose: Preauth RCE and mTLS Bypass on Millions of Devices]() Original publisher: [Read original article]() Author: Simone Margaritelli Published: 2026-04-01T22:00:00Z Content type: article Language: en Sources: [evilsocket]() Topics: [Mongoose](), [Vulnerabilities](), [Security](), [Embedded Systems](), [Internet of things](), [C](), [cross-platform](), [HTTP](), [MQTT](), [WebSocket]() Tags: [authentication-bypass](), [buffer-overflow](), [c](), [cesanta](), [cross-platform](), [cve](), [cve-2026-5244](), [cve-2026-5245](), [cve-2026-5246](), [cybersecurity](), [embedded](), [embedded-devices](), [embedded-systems](), [exploit](), [heap-overflow](), [http](), [https](), [industrial-control](), [iot](), [iot-security](), [library](), [mdns](), [mips](), [mongoose](), [mqtt](), [mtls](), [rce](), [responsible-disclosure](), [security](), [stack-overflow](), [tls](), [vulnerability-research]() ### AI overview The article reports three independently exploitable vulnerabilities in Mongoose v7.20, an embedded C networking library used in IoT devices: an mTLS authentication bypass, a preauthentication heap-overflow RCE through client public-key parsing, and a preauthentication RCE through mDNS over UDP. Mongoose v7.21 reportedly includes patches for the issues, which were assigned CVE-2026-5244, CVE-2026-5245, and CVE-2026-5246. ### Source excerpt So, Mongoose. I ## TP-Link Tapo C200: Hardcoded Keys, Buffer Overflows and Privacy in the Era of AI Assisted Reverse Engineering DevFeed: [TP-Link Tapo C200: Hardcoded Keys, Buffer Overflows and Privacy in the Era of AI Assisted Reverse Engineering]() Original publisher: [Read original article]() Author: Simone Margaritelli Published: 2025-12-17T23:00:00Z Content type: article Language: en Sources: [evilsocket]() Topics: [Reverse Engineering](), [Vulnerabilities](), [Security](), [Embedded Systems](), [Android](), [Amazon Web Services]() Tags: [ai](), [ai-assisted-reverse-engineering](), [android](), [assembly](), [aws](), [china](), [cve](), [cve-2025-14299](), [cve-2025-14300](), [cve-2025-8065](), [cybersecurity](), [embedded-devices](), [embedded-systems](), [exploit](), [firmware](), [ghidra](), [ghidramcp](), [hardcoded-credentials](), [integer-overflow](), [iot](), [iot-security](), [memory](), [mips](), [privacy](), [re](), [reverse-engineering](), [reversing](), [security](), [security-research](), [security-vulnerabilities](), [tapo-c200](), [tapo-camera](), [tp-link](), [tplink](), [vulnerability-research]() ### AI overview This article describes an AI-assisted reverse-engineering investigation of TP-Link Tapo C200 camera firmware. The author reports finding several security vulnerabilities affecting about 25,000 devices directly exposed on the internet, and discusses the tools and process used. ### Source excerpt Hi friends and welcome to the last post for this year! Whenever someone asks me how to get started with reverse engineering, I always giv ## How to Write an Agent DevFeed: [How to Write an Agent]() Original publisher: [Read original article]() Author: Simone Margaritelli Published: 2025-03-13T01:36:08Z Content type: tutorial Language: en Sources: [evilsocket]() Topics: [AI Development](), [function calling](), [LLMs]() Tags: [adk](), [agent](), [agent-development-kit](), [agent-evals](), [ai](), [autonomous-agents](), [blog](), [cybersecurity](), [evals](), [evaluations](), [function-calling](), [how-to](), [howto](), [llm](), [nerve](), [nerve-adk](), [project-release](), [tool-use]() ### AI overview This tutorial explains how software agents use models to select tools in a loop, and how function calling lets language models invoke tools. It introduces Nerve as a project intended to simplify implementing an agent and discusses executing tool calls and returning their outputs to the model. ### Source excerpt Hello friends. This blog post was supposed to be the second part of this re ## Attacking UNIX Systems via CUPS, Part I DevFeed: [Attacking UNIX Systems via CUPS, Part I]() Original publisher: [Read original article]() Author: Simone Margaritelli Published: 2024-09-26T14:51:30Z Content type: article Language: en Sources: [evilsocket]() Topics: [vulnerability](), [Security](), [Unix](), [Exploit](), [gnu linux](), [systems]() Tags: [bugs](), [cups](), [cups-browsed](), [cve](), [cve-2024-47076](), [cve-2024-47175](), [cve-2024-47176](), [cve-2024-47177](), [cybersecurity](), [disclosure](), [exploit](), [gnu-linux](), [hacking](), [ipp](), [lan](), [linux-security](), [mdns](), [no-authentication](), [port](), [print-services](), [printer](), [printers](), [printing](), [rce](), [responsible-disclosure](), [security](), [udp](), [unauthenticated-access](), [unix](), [vulnerability-research](), [zeroconf]() ### AI overview A security writeup describes multiple vulnerabilities in CUPS components affecting GNU/Linux and other UNIX systems. It reports that remote unauthenticated attackers may replace printer IPP URLs and trigger arbitrary command execution when a print job starts, with attacks possible over the public internet or via spoofed LAN advertisements. ### Source excerpt Hello friends, this is the first of two, possibly three (if and when I have time to finish the Windows research) writeups. We will start ## Introducing Bettercap 2.4.0: CAN-Bus Hacking, WiFi Bruteforcing and Builtin Web UI DevFeed: [Introducing Bettercap 2.4.0: CAN-Bus Hacking, WiFi Bruteforcing and Builtin Web UI]() Original publisher: [Read original article]() Author: Simone Margaritelli Published: 2024-09-13T10:46:25Z Content type: release Language: en Sources: [evilsocket]() Topics: [Hacking](), [Security](), [Fuzzing/Fuzz testing](), [Protocol (disambiguation)](), [Hardware](), [ui]() Tags: [automotive-security](), [bettercap](), [can-bus](), [canbus](), [car](), [car-hacking](), [cybersecurity](), [features](), [fuzzing](), [hacking](), [hardware](), [ics](), [industrial](), [industrial-control](), [offensive-tools](), [protocol](), [release](), [socketcan](), [webui](), [wifi](), [wifi-bruteforcing](), [wireless-security]() ### AI overview The article announces bettercap 2.4.0, a major release that adds functionality for car and industrial control system security research. It describes a new CAN-bus module for reading, replaying, injecting, and fuzzing frames, parsing frames with DBC files, and detecting ECUs, alongside other new features and fixes. ### Source excerpt I'm happy to announce, after quite some time, the new bettercap 2.4.0 major release. Other than including a plethora of long due fixes (additionally to what the recent 2.33.0 already fixed), it also packs a few new functionalities that extend its reach to car and industrial control system hacking. It'll possibly take me some time to update the documentation on the official website so I'm here today to write a bit about the new features. Also remember that you can use the help, help ui, help can and help wifi commands to check all the new options and added functionalities. ## Legba: An Asynchronous Rust Framework for Authentication Bruteforcing DevFeed: [Legba: An Asynchronous Rust Framework for Authentication Bruteforcing]() Original publisher: [Read original article]() Author: Simone Margaritelli Published: 2023-11-02T16:46:32Z Content type: opinion Language: en Sources: [evilsocket]() Topics: [Tool](), [Rust](), [Tokio](), [Authentication](), [Code]() Tags: [amqp](), [async](), [asynchronous](), [authentication](), [benchmark](), [bruteforce](), [cassandra](), [csrf-token](), [dns-subdomain-enumeration](), [http](), [hydra](), [imap](), [kerberos](), [kerberos-pre-authentication](), [ldap](), [legba](), [mongodb](), [mssql](), [multi-protocol](), [mysql](), [ntlm](), [offensive-tools](), [oracle](), [password](), [pgsql](), [pop3](), [project-release](), [rdp](), [red-team](), [rust](), [tokio](), [tool](), [wordlist]() ### AI overview The article presents Legba, a Rust-based authentication bruteforcing tool developed as an asynchronous and modular alternative to tools such as THC Hydra. It discusses the motivation, design objectives, supported features, and a limited localhost benchmark comparing Legba with Hydra. ### Source excerpt During the last few weeks I've been working on a new tool that started as a way for me to become more familiar with Rust and its ## Reverse Engineering the Apple MultiPeer Connectivity Framework DevFeed: [Reverse Engineering the Apple MultiPeer Connectivity Framework]() Original publisher: [Read original article]() Author: Simone Margaritelli Published: 2022-10-20T11:05:13Z Content type: tutorial Language: en Sources: [evilsocket]() Topics: [Reverse Engineering](), [Protocol (disambiguation)](), [Python](), [client](), [Network](), [Framework]() Tags: [apple](), [cybersecurity](), [facetime](), [framework](), [ice](), [ios](), [iphone](), [logic-pro](), [mac](), [macos-security](), [mcpeer](), [mcpeerid](), [mdns](), [mpc-framework](), [multipeer](), [multipeerconnectivity](), [network](), [network-packets](), [network-protocol](), [ospf](), [proprietary-protocol](), [protocol-reversing](), [python](), [re](), [reverse-engineering](), [stun](), [tcp](), [undocumented](), [wireshark]() ### AI overview A reverse-engineering investigation of Apple's undocumented Multipeer Connectivity Framework. The article examines its custom TCP protocol, documents network packets, and describes a Python proof-of-concept client that discovers servers, establishes connections, and exchanges application data. It also reports parser vulnerabilities and discusses session spoofing. ### Source excerpt Some time ago I was using Logic Pro to record some of my music and I needed a way to start and stop the recording from an iPhone, so I found about Logic Remote and was quite happy with it. After the session, the hacker in me became curious about how the tools were communicating with each other, so I quickly started Wireshark while establishing a connection and saw something that tickled my curiosity even more: some of the data, such as the client and server names, were transmitted in cleartext on what it seemed a custom (and as typical of Apple, undocumented) TCP protocol ("stevie" being the hostname of my Mac): Using lsof confirmed that this was indeed the communication between the client phone and Logic listening on port 56076: Initially I tought this was just some Logic Pro specific protocol and very lazily started looking into it, without much success mostly due to lack of motivation given the very limited scope of the research. After a while I tweeted asking if anyone had ever seen anything like it. @isComputerOn pointed out that this looked a lot like a protocol that has been partially reversed and presented by Alban Diquet back in 2014. Unfortunately, however brilliant, this research covers the protocol at a very high level and doesn't really document the packets, their fields and how to establish a connection from anything but a client using the Apple framework. However, this helped me a lot in two ways: first it helped me realize this was not just Logic Pro specific, but that it was part of the Multipeer Connectivity Framework, and gave me a few hints about the general logic of the protocol itself. With renewed curiosity and motivation then I jumped into this rabbit hole and managed to reverse engineer all network packets. This allowed me to write a Python proof of concept client that automatically discovers any MPC servers, initializes the connection and succesfully exchanges application specific data packets. Moreover, while sending crafted packets and at ## Process Behaviour Anomaly Detection Using eBPF and Unsupervised-Learning Autoencoders DevFeed: [Process Behaviour Anomaly Detection Using eBPF and Unsupervised-Learning Autoencoders]() Original publisher: [Read original article]() Author: Simone Margaritelli Published: 2022-08-15T14:06:05Z Content type: tutorial Language: en Sources: [evilsocket]() Topics: [eBPF](), [Processes](), [Linux Kernel](), [Learning]() Tags: [ai](), [anomaly-detection](), [artificial-intelligence](), [autoencoder](), [bcc](), [cybersecurity](), [deep-learning](), [deep-neural-networks](), [defensive-security](), [dnn](), [ebpf](), [github](), [kernel](), [kprobe](), [kretprobe](), [linux](), [linux-security](), [machine-learning](), [neural-networks](), [process-anomaly-detection](), [process-behaviour](), [raw-syscalls](), [runtime-protection](), [sys-enter](), [syscall-tracing](), [tensorflow](), [tracepoint](), [unsupervised-learning]() ### AI overview This tutorial describes using eBPF syscall tracing and an unsupervised autoencoder to detect process behavior anomalies at runtime. It explains an approach that models syscall frequency without requiring an explicit allowlist and discusses potential detection of exploitation, denial-of-service, and other attacks. ### Source excerpt Hello everybody, I hope you've been enjoying this summer after two years of Covid and lockdowns :D In this post I'm going to describe how ## Hide Your Servers in Plain Sight, Presenting ShieldWall DevFeed: [Hide Your Servers in Plain Sight, Presenting ShieldWall]() Original publisher: [Read original article]() Author: Simone Margaritelli Published: 2021-02-13T14:34:28Z Content type: release Language: en Sources: [evilsocket]() Topics: [Server](), [Encryption](), [Go Language](), [Raspberry Pi]() Tags: [api](), [cybersecurity](), [defensive-security](), [encryption](), [firewall](), [go](), [golang](), [iptables](), [network-security](), [project-release](), [raspberry-pi](), [remote-firewall-instrumentation](), [secret](), [server](), [server-hardening](), [servers](), [shieldwall]() ### AI overview This article introduces ShieldWall, a project intended to keep personal or sensitive services accessible across changing device IP addresses while limiting access to authorized devices at the packet level. It discusses Arc as a use case and mentions encrypted data, public servers, and hidden infrastructure for red team operations. ### Source excerpt Long time no see friends! Despite this break period ended up not being as long as I hoped ## Pwnagotchi 1.0.0: An AI-assisted Raspberry Pi tool for WiFi security testing DevFeed: [Pwnagotchi 1.0.0: An AI-assisted Raspberry Pi tool for WiFi security testing]() Original publisher: [Read original article]() Author: Simone Margaritelli Published: 2019-10-19T08:45:28Z Content type: article Language: en Sources: [evilsocket]() Topics: [Artificial Intelligence](), [Hacking](), [Raspberry Pi](), [REST API]() Tags: [ai](), [artificial-intelligence](), [bettercap](), [cuda](), [cybersecurity](), [deep-learning](), [deep-neural-networks](), [deep-reinforcement-learning](), [dnn](), [e-paper](), [hacking](), [handshake-capture](), [handshakes](), [low-power](), [machine-learning](), [monitor-mode](), [neural-networks](), [nvidia](), [pi](), [poc](), [portable-hacking](), [pwnagotchi](), [raspberry-pi](), [reinforcement-learning](), [release](), [wifi](), [wifi-hacking](), [wireless-security]() ### AI overview The article recounts the development and release of Pwnagotchi 1.0.0, a Raspberry Pi-based project that uses bettercap's REST API and adaptive algorithms to improve WiFi handshake collection and related security-testing capabilities. It describes the project's evolution from an initial Python proof of concept and discusses the use of a Waveshare e-Paper display for portable, low-power operation. ### Source excerpt This is the story of a summer project that started out of boredom and that evolved into something incredibly fun and unique. It is also the story of how that project went from being discussed on a porch by just two people, to having a community made of almost 700 awesome people (and counting!) that gathered, polished it and made today's release possible. TL;DR: You can download the 1.0.0 .img file from here, then just follow the instructions. If you want the long version instead, sit back, relax and enjoy the ride. Let me tell you: it's going to be quite a long journey compared to my usual blog posts, but it'll be worth it (i hope) and fun (i hope even harder). Let's begin ... ## How to Create a Malware Detection System With Machine Learning DevFeed: [How to Create a Malware Detection System With Machine Learning]() Original publisher: [Read original article]() Author: Simone Margaritelli Published: 2019-05-22T21:59:13Z Content type: tutorial Language: en Sources: [evilsocket]() Topics: [Malware](), [Machine Learning & Artificial Intelligence](), [Neural Network](), [Windows](), [Code]() Tags: [ai](), [antivirus](), [binary-analysis](), [classification](), [computer-virus](), [cuda](), [cybersecurity](), [deep-learning](), [deep-neural-networks](), [deployment](), [dnn](), [ergo](), [feature-engineering](), [features](), [gpu](), [how-to](), [keras](), [machine-learning](), [malware](), [malware-detection](), [neural-network](), [neural-networks](), [nvidia](), [portable-executable](), [security-research](), [tensorflow](), [tf](), [windows-pe]() ### AI overview A practical tutorial on using machine learning and artificial neural networks to detect Windows malware without relying on an explicit signatures database. It uses malware detection as an example for the ergo project, which automates parts of model creation, data encoding, GPU training, benchmarking, and deployment. ### Source excerpt In this post we'll talk about two topics I love and that have been central elements of my (private) research for the last ~7 years: machi ## Pwning WPA/WPA2 Networks With Bettercap and the PMKID Client-Less Attack DevFeed: [Pwning WPA/WPA2 Networks With Bettercap and the PMKID Client-Less Attack]() Original publisher: [Read original article]() Author: Simone Margaritelli Published: 2019-02-13T15:53:31Z Content type: tutorial Language: en Sources: [evilsocket]() Topics: [Networks](), [passwords](), [client](), [GPU]() Tags: [attacks](), [bettercap](), [cybersecurity](), [deauth](), [handshake](), [hashcat](), [how-to](), [monitor-mode](), [networks](), [packet-injection](), [password-cracking](), [passwords](), [pmkid](), [rsn](), [rsn-pmkid](), [wifi-hacking](), [wireless-security](), [wpa](), [wpa2]() ### AI overview This tutorial explains new WiFi features in bettercap, including automated EAPOL handshake capture and a PMKID client-less attack against WPA/WPA2 access points. It also covers deauthentication-based capture workflows and preparing captured files for hashcat password cracking. ### Source excerpt In this post, I'll talk about the new WiFi related features that have been recently implemented into bettercap, starting from how the EAPOL 4-way handshake capturing has been automated, to a whole new type of attack that will allow us to recover WPA PSK passwords of an AP without clients. We'll start with the assumption that your WiFi card supports monitor mode and packet injection (I use an AWUS1900 with this driver), that you have a working hashcat (v4.2.0 or higher is required) installation (ideally with GPU support enabled) for cracking and that you know how to use it properly either for dictionary or brute-force attacks, as no tips on how to tune the masks and/or generate proper dictionaries will be given :) On newer macOS laptops, the builtin WiFi interface `en0` already supports monitor mode, meaning you won't need a Linux VM in order to run this :) ## Presenting Project Ergo: How to Build an Airplane Detector for Satellite Imagery With Deep Learning DevFeed: [Presenting Project Ergo: How to Build an Airplane Detector for Satellite Imagery With Deep Learning]() Original publisher: [Read original article]() Author: Simone Margaritelli Published: 2018-11-22T17:15:50Z Content type: tutorial Language: en Sources: [evilsocket]() Topics: [Keras](), [Tensorflow](), [Framework](), [Deep learning](), [Deep neural networks](), [datasets](), [Open Source](), [Code](), [Development](), [Back end](), [Python](), [Shell]() Tags: [cnn](), [code](), [computer-vision](), [convolutional-neural-networks](), [cpu](), [cuda](), [cudnn](), [cybersecurity](), [deep-learning](), [deep-neural-networks](), [dnn](), [ergo](), [how-to](), [image-classification](), [keras](), [machine-learning](), [neural-networks](), [nvidia](), [open-source](), [planes](), [planes-detector](), [planesnet](), [project-release](), [python](), [shell](), [tensorflow](), [tf](), [train](), [training](), [tutorial]() ### AI overview The article introduces Project Ergo, an open-source framework and manager for Keras-based machine-learning projects. It demonstrates prototyping, training, and testing a convolutional neural network with the PlanesNet dataset to build an airplane detector for satellite imagery, including CPU and GPU setup considerations. ### Source excerpt It's been a while that i've been quite intensively playing with Deep Learning both for work related research and personal projects. More specifically, I've been using the Keras framework on top of a TensorFlow backend for all sorts of stuff. From big and complex projects for malware detection, to smaller and simpler experiments about ideas i just wanted to quickly implement and test - it didn't really matter the scope of the project, I always found myself struggling with the same issues: code reuse over tens of crap python and shell scripts, datasets and models that are spread all over my dev and prod servers, no real standard for versioning them, no order, no structure. So a few days ago I started writing what it was initially meant to be just a simple wrapper for the main commands of my training pipelines but quickly became a full-fledged framework and manager for all my Keras based projects. Today I'm pleased to open source and present project Ergo by showcasing an example use-case: we'll prototype, train and test a Convolutional Neural Network on top of the PlanesNet raw dataset in order to build an airplane detector for satellite imagery. ## Project PITA: Build a Mini Mass Deauther Using Bettercap and a Raspberry Pi Zero W DevFeed: [Project PITA: Build a Mini Mass Deauther Using Bettercap and a Raspberry Pi Zero W]() Original publisher: [Read original article]() Author: Simone Margaritelli Published: 2018-07-28T17:01:56Z Content type: tutorial Language: en Sources: [evilsocket]() Topics: [Raspberry Pi](), [Linux](), [Network](), [configuration](), [ssh](), [Bluetooth](), [clients](), [file]() Tags: [bettercap](), [ble](), [bluetooth](), [btnap](), [cybersecurity](), [deauth](), [handshake-capture](), [kali](), [linux](), [monitor-mode](), [packet-injection](), [pi](), [portable-hacking](), [project](), [raspberry](), [raspberry-pi](), [rpi](), [rpi-zero-w](), [rpi0w](), [wifi](), [wireless-security](), [wpa2](), [writeup](), [zero]() ### AI overview A writeup showing how to build a pocket-sized WiFi deauthenticator with a Raspberry Pi Zero W, Kali Linux, Nexmon drivers, and bettercap. It covers WiFi scanning, deauthentication packets, WPA2 handshake capture, initial SSH and WiFi configuration, and Bluetooth access. ### Source excerpt A few days ago I started playing with some idea I had from a few weeks already, using a Raspberry Pi Zero W to make a mini WiFi deauthenticator: something in my pocket that periodically jumps on all the channels in the WiFi spectrum, collects information about the nearby access points and their connected clients and then sends a deauthentication packet to each one of them, resulting in some sort of WiFi jammer on the 802.11 level. As an interesting "side effect" of this jammer (the initial intent was purely for the lulz) is that the more it deauths, the higher the changes to also sniff WPA2 handshakes. Thanks to the awesome work of the Kali and Nexmon communities in packaging the nexmon drivers and utilities and to the recent changes we released in bettercap, this was very easy to setup and to script and given the interest the tweet had I thought to share this writeup :) This awesome case has been designed by @elkentaro and can be found on [his Thingverse page](https://www.thingiverse.com/thing:3018480). ## A Go Developer's Subjective Critiques of the Language DevFeed: [A Go Developer's Subjective Critiques of the Language]() Original publisher: [Read original article]() Author: Simone Margaritelli Published: 2018-03-14T22:39:09Z Content type: opinion Language: en Sources: [evilsocket]() Topics: [Go Language](), [Programming]() Tags: [cybersecurity](), [design-patterns](), [developing](), [go](), [golang](), [language-critique](), [oop](), [opinion](), [programming](), [software-development]() ### AI overview A Go programmer presents subjective criticisms of the language to offer a more balanced account of their experience. The author says Go may still be a better choice for several applications and does not frame the piece as a Go-versus-Rust debate. ### Source excerpt After my last post and generally the kind of indirect advertising I'm doing to the Go programming language for a few months now, I heard about and talked with a lot of people who started being interested in the language, so for once I decided to write what I don't like about it instead, to provide a more balanced perspective of what's my experience so far and maybe let some of those people realize that Go is not the right choice for their projects after all. NOTE 1 It's important to say that some, if not most of the things I'm about to write are purely subjective and related to my programming habits, they do not necessarily represent so called "best practices" and should not be taken like so. Moreover, I'm still a Go noob, some of the things I'm going to say might just be inaccurate / wrong, in which case feel free to correct me and teach me something new, please :D NOTE 2 Before we start: I love this language and I already explained why I still consider it a better choice for several applications, but I'm not interested in an opinion war about Go vs Rust, or Go vs whatever ... use what you think it's best for what you have to do: if that's Rust go for it, if you think it's binary code you send to the processor by using your nipples to inject faults into some data bus, go for it, both cases, code and let code, life is too short for being a language hipster. ## Bettercap 2.0 Released as a Go-Based Framework for MITM Attacks and Network Monitoring DevFeed: [Bettercap 2.0 Released as a Go-Based Framework for MITM Attacks and Network Monitoring]() Original publisher: [Read original article]() Author: Simone Margaritelli Published: 2018-02-27T19:37:20Z Content type: release Language: en Sources: [evilsocket]() Topics: [Network](), [Monitoring](), [Go Language](), [Raspberry Pi](), [Android](), [macOS]() Tags: [2](), [android](), [bettercap](), [ble](), [cybersecurity](), [go](), [golang](), [macos](), [mitm](), [monitoring](), [network](), [network-attacks](), [offensive-tools](), [project-release](), [raspberry-pi](), [release](), [traffic-interception](), [wifi]() ### AI overview The article announces bettercap 2.0, a complete reimplementation of the Man-in-the-Middle attack framework. It describes a move from Ruby to compiled Go, with improved concurrency, performance, and reduced resource usage, alongside support for network monitoring, Wi-Fi and BLE attacks, and multiple platforms. ### Source excerpt It's with immense pleasure that I announce the release of the second generation of bettercap, a complete reimplementation of the most complete and advanced Man-in-the-Middle attack framework. This release not only brings MITM attacks to the next level, but it aims to be the reference framework for network monitoring (we <3 blueteams too), 802.11, BLE attacks and more! :D ベッターキャップ！ ## DIY Portable Secrets Manager With a Raspberry Pi Zero and ARC DevFeed: [DIY Portable Secrets Manager With a Raspberry Pi Zero and ARC]() Original publisher: [Read original article]() Author: Simone Margaritelli Published: 2017-12-07T16:42:48Z Content type: tutorial Language: en Sources: [evilsocket]() Topics: [Raspberry Pi](), [passwords](), [Encryption](), [SQLite](), [API](), [Go](), [HTML5](), [JavaScript](), [Markdown](), [ui](), [Server]() Tags: [aes](), [api](), [arc](), [arcd](), [cybersecurity](), [database](), [encryption](), [go](), [golang](), [html5](), [javascript](), [markdown](), [notes](), [oss](), [password-manager](), [passwords](), [pi](), [portable-hacking](), [project-release](), [raspberry-pi](), [secrets](), [self-hosted](), [terminal]() ### AI overview This tutorial presents ARC, a self-hosted secrets manager designed to store encrypted passwords, notes, and files and synchronize access across devices without relying on cloud hosting or a paid server. It describes a Go REST API server using SQLite and an HTML5/JavaScript browser client, then begins configuring the system on a Raspberry Pi Zero. ### Source excerpt For the last few days I've been working on a new project which I developed for very specific needs and reasons: I need to store safely (encrypted) my passwords, sensitive files, notes, etc. I need to access them from anywhere, with every possible device ( desktop, mobile, terminal ). I need those objects to be syncronized accros all my devices. I don't want to use "the cloud". I don't want to pay for a server. I don't want to enable port forwarding and host it myself with DynDNS or alikes. So I wrote ARC. ## This Is Not a Post About BLE, Introducing BLEAH DevFeed: [This Is Not a Post About BLE, Introducing BLEAH]() Original publisher: [Read original article]() Author: Simone Margaritelli Published: 2017-09-23T15:06:56Z Content type: tutorial Language: en Sources: [evilsocket]() Topics: [Bluetooth](), [Security](), [Fuzzing/Fuzz testing](), [Internet of things](), [Tool](), [Open Source]() Tags: [ble](), [bleah](), [bluetooth](), [bluetooth-low-energy](), [btle](), [cybersecurity](), [fuzzing](), [hack](), [iot](), [iot-security](), [offensive-tools](), [open-source](), [security](), [tools](), [wireless-security]() ### AI overview An introduction to hacking Bluetooth Low Energy devices that also presents BLEAH, an open-source tool. The article discusses BLE's discoverability, connection behavior, data access, and lack of built-in protocol security, while noting that automatic fuzzing features were kept in a private fork. ### Source excerpt This is not a post about BLE, but rather on how to hack it ... well, to be honest, BLE devices are usually very easy to hack, so it's just a quick intro to it, I'll also take the chance to open source one of the last tools I've made and that I kept private so far. I moved the features I thought to be dangerous ( aka: auto fuzzing all the BLE things and bring chaos ) in a private fork which will stay private, however it's not that complicated to chain bleah with other tools ( cough ... radamsa ... cough ) and have lots of fun. Oh and this is also because someone asked me some intro on BLE, so yeah, his fault. ## Hacking a Herb Vaporizer to Set Its Temperature Limit From 190C to 6553.5C Remotely DevFeed: [Hacking a Herb Vaporizer to Set Its Temperature Limit From 190C to 6553.5C Remotely]() Original publisher: [Read original article]() Author: Simone Margaritelli Published: 2017-08-25T01:10:53Z Content type: opinion Language: en Sources: [evilsocket]() Topics: [Hacking](), [Bluetooth](), [Security](), [Hardware]() Tags: [ble](), [bluetooth](), [bluetooth-low-energy](), [btle](), [crafty](), [crafty-vaporizer](), [cybersecurity](), [embedded-devices](), [firmware](), [hacking](), [iot-security](), [linux](), [low-energy](), [no-authentication](), [protocol-reversing](), [responsible-disclosure](), [security](), [terminal](), [vaporizer]() ### AI overview The article describes reverse engineering the Crafty vaporizer's mobile application and Bluetooth Low Energy interface. It reports that device descriptors could be read and written without authentication and that the temperature value was stored as two bytes, allowing a remote attempt to change the limit from 190°C to 6553.5°C. The author did not test the modified setting. ### Source excerpt Tonight my brain decided, instead of sleeping (why even bother trying, right?), to start a new short adventure in the Bluetooth Low Energy world. I'm a happy Crafty vaporizer owner and as I discovered by chance, I can access it using my laptop.