Salta al contenuto principale

Rolling Foam Cutter Gives Mattress a Close Shave


There’s many different reasons why somebody might have to hack together their own solution to a problem. It could be to save money, or to save time. Occasionally it’s because the problem is unique enough that there might not be an accepted solution, so you’re on your own to create one. We think the situation that [Raph] recently found himself in was a combination of several of these aspects, which makes his success all the sweeter.

The problem? [Raph] had a pair of foam mattresses from his camper van that needed to be made thinner — each of the three inch (7.62 cm) pieces of foam needed to have one inch (2.5 cm) shaved off as neatly and evenly as possible. Trying to pull that off over the length of a mattress with any kind of manual tools was obviously a no-go, so he built a low-rider foam cutter.

With the mattresses laying on the ground, the idea was to have the cutter simply roll across them. The cutter uses a 45″ (115 cm) long 14 AWG nichrome wire that’s held in tension with a tension arm and bungee cords, which is juiced up with a Volteq HY2050EX 50 V 20 A variable DC power supply. [Raph] determined the current experimentally: the wire failed at 20 A, and cutting speed was too low at 12 A. In the end, 15 A seemed to be the sweet spot.

The actual cutting process was quite slow, with [Raph] finding that the best he could do was about 1/8″ (3 mm) per second on the wider of the two mattresses. While the result was a nice flat cut, he does note that at some point the mattresses started to blister, especially when the current was turned up high. We imagine this won’t be a big deal for a mattress though, as you can simply put that side on the bottom.

In the end, the real problem was the smell. As [Raph] later discovered, polyurethane foam is usually cut mechanically, as cutting it with a hot wire gives off nasty fumes. Luckily he had plenty of ventilation when he was making his cuts, but he notes that the mattresses themselves still have a stink to them a couple days later. Hopefully they’ll finish outgassing before his next camping trip.

As you can imagine, we’ve covered a great number of DIY foam cutters over the years, ranging from the very simple to computerized marvels. But even so, there’s something about the project-specific nature of this cutter that we find charming.


hackaday.com/2025/03/24/rollin…


L’impegno di Fortinet nel secure by design: misurare i progressi nella sicurezza informatica


A cura di Aldo Di Mattia, Director of Specialized Systems Engineering and Cybersecurity Advisor Italy and Malta di Fortinet

All’inizio del 2024, CISA (Cybersecurity and Infrastructure Security Agency) ha introdotto il Secure by Design Pledge, che delinea sette obiettivi per lo sviluppo e l’implementazione di software sicuri. Fortinet è stata tra i primi firmatari e sostenitori di questa iniziativa, che si allinea con i processi di sviluppo dei propri prodotti, da tempo basati sui principi del secure by design e del secure by default.

Fortinet lavora costantemente per incrementare l’installazione delle patch di sicurezza rilasciate, in linea con uno degli obiettivi stabiliti dalla CISA nel Secure by Design Pledge. Questo impegno ha rappresentato un’opportunità importante per misurare i progressi e determinare se le modifiche apportate stavano migliorando in modo tangibile la posizione di sicurezza dei clienti.
Aldo Di Mattia, Director of Specialized Systems Engineering and Cybersecurity Advisor Italy and Malta di Fortinet
In primo luogo, Fortinet ha cercato di capire perché alcuni clienti non aggiornavano i loro dispositivi quando venivano rilasciati gli aggiornamenti. Le ragioni più ricorrenti erano due:

  • Preoccupazione di destabilizzare una rete funzionante
  • Mancanza di tempo e risorse

Raggiunta questa consapevolezza, Fortinet ha lavorato per risolvere entrambi i problemi, semplificando il processo di patching nonostante le loro difficoltà specifiche. Qui di seguito sono illustrati i passi compiuti per risolvere ogni problema e i dati raccolti per determinare se questi sforzi sono stati coronati da successo.

Sfida del cliente n. 1: preoccupazioni per la destabilizzazione di una rete funzionante


Pur comprendendo che può essere problematico dare disservizio ad una rete funzionante, è fondamentale che i team IT e di sicurezza applichino le patch il prima possibile per ridurre la possibilità che gli aggressori sfruttino una vulnerabilità. Fortinet raccomanda sempre ai clienti di effettuare un’analisi immediata del rischio e di effettuare l’aggiornamento più rapidamente possibile. Allo stesso tempo, l’azienda comprende perché non si voglia bloccare un’infrastruttura di rete, dal momento che i responsabili IT e della sicurezza sono costantemente in bilico tra il potenziamento delle misure di sicurezza e l’eventuale interruzione della normale operatività.

Come Fortinet ha affrontato questa sfida


Per semplificare il processo decisionale dei clienti in merito a quando e come applicare una patch rilasciata da Fortinet, sono state introdotte delle etichette di funzionalità e maturità per le release del firmware. Di conseguenza, gli amministratori possono accertare rapidamente se il firmware contiene solo correzioni di bug o se la release contiene funzionalità supplementari. La messa a disposizione di questi dati aggiuntivi fornisce agli amministratori di rete, in modo rapido e chiaro, informazioni utili per le loro valutazioni e una maggiore affidabilità nelle loro decisioni su come e quando implementare un aggiornamento.

Ad oggi, i clienti hanno risposto che in questo modo è molto più semplice prendere decisioni basate sul rischio e sull’adozione di una release nei loro ambienti, in base alla criticità della loro attività e alla necessità di nuove funzionalità specifiche.

Sfida del cliente n. 2: mancanza di tempo e di risorse


Fortinet lavora con clienti di tutte le dimensioni e operanti in tutti i settori. Una cosa che accomuna quasi tutte le organizzazioni è l’impatto della carenza di competenze in materia di cybersecurity. Questo è evidente dai numeri seguenti, che mostrano un’adozione relativamente lenta delle patch da parte dei clienti (circa 40.000 aggiornamenti al mese), nonostante la presenza di una fix di una “high-severity” inclusa nella release 7.2.5.

Il tasso di aggiornamento è raddoppiato dalla release 7.2.5 alla 7.2.6, rappresentato nel grafico seguente. Questo andamento è stato confermato con le release successive, in quanto i clienti diventano sempre meno preoccupati delle “novità” presenti nelle release.

Secondo il rapporto 2024 Global Cybersecurity Skills Gap di Fortinet, nell’ultimo anno, l’86% dei leader d’azienda in Italia ha dichiarato di aver subito una violazione che può essere parzialmente attribuita alla mancanza di skill di cybersecurity nei team che si occupano di rete e di sicurezza. L’impatto è considerevole se si tiene in conto che il 58% dei partecipanti ha dichiarato di attribuire tali attacchi alla mancanza di consapevolezza sul tema della sicurezza da parte delle loro organizzazioni e dei propri dipendenti. Non da ultimo, il 44% ha evidenziato come siano stati necessari da 1 a 3 mesi per recuperare i danni derivanti dagli attacchi subiti.

Tuttavia, nonostante la scarsità reale o percepita di risorse in un’organizzazione, gli aggiornamenti devono avvenire a un ritmo più veloce.

Figura 1: Tasso di aggiornamento dei clienti Fortinet dalla versione FortiOS 7.2.5 alla 7.2.6

Come Fortinet ha affrontato questa sfida


Per contribuire ad aumentare l’adozione delle patch, Fortinet ha scelto di utilizzare un metodo simile a quello utilizzato dal settore della telefonia mobile per l’aggiornamento automatico dei dispositivi. Nella fase iniziale di prova, i dispositivi di fascia bassa per i piccoli uffici e per gli uffici domestici, oltre che per le piccole e medie imprese, sono stati impostati per l’aggiornamento automatico nelle seguenti condizioni:

  • La funzione di aggiornamento automatico è abilitata come impostazione predefinita sui dispositivi di fascia bassa (100F e inferiori). Può essere abilitata dall’amministratore anche su altri dispositivi.
  • Il dispositivo non è gestito centralmente da FortiManager.
  • L’aggiornamento passerà solo alla release successiva e più stabile all’interno dello stessa versione, per cui:
    • L’aggiornamento da 7.2.8 (maturo) a 7.2.9 (maturo) verrà effettuato.
    • Non verrà eseguito l’aggiornamento da 7.2.8 (maturo) a 7.4.4 (feature).


  • I clienti possono disattivare questa funzione in qualsiasi momento, se lo desiderano.

Questa funzione di aggiornamento automatico di FortiOS è stata introdotta nella versione 7.2.6 ed è stata attivata per la prima volta con la versione 7.2.7. I risultati sono immediatamente evidenti, come mostrato di seguito:

Figura 2: Tasso di aggiornamento tra i clienti Fortinet dopo l’implementazione della funzione di aggiornamento automatico

La versione 7.2.7 è stata implementata su quasi 200.000 dispositivi in pochi giorni, riducendo la possibilità per gli attaccanti informatici di sfruttare le vulnerabilità corrette nell’aggiornamento.

Questa funzione sarà estesa ad altri modelli nelle prossime release.

Semplificare il percorso verso il rafforzamento della postura di sicurezza


Nel tempo, queste iniziative continueranno a migliorare la sicurezza dei clienti Fortinet e a impedire agli attaccanti informatici di sfruttare le vulnerabilità note. Misurare i progressi rispetto ai sette obiettivi delineati nel CISA Secure by Design Pledge permette all’azienda di capire il successo degli sforzi e offre l’opportunità di trovare nuovi modi per semplificare ulteriormente la sicurezza dei propri clienti.

Si tratta di un altro passo avanti per mantenere l’impegno preso dall’azienda di continuare a sviluppare e innovare anche in questo ambito.

L'articolo L’impegno di Fortinet nel secure by design: misurare i progressi nella sicurezza informatica proviene da il blog della sicurezza informatica.


Build a Starship Starship Bridge Simulator With EmptyEpsilon


Next time on Star Trek: EmptyEpsilon... (Credit: EmptyEpsilon project)

Who hasn’t dreamed of serving on the bridge of a Star Trek starship? Although the EmptyEpsilon project isn’t adorned with the Universe-famous LCARS user interface, it does provide a comprehensive simulation scenario, in a multiplayer setting. Designed as a LAN or WAN multiplayer game hosted by the server that also serves as the main screen, four to six additional devices are required to handle the non-captain tasks. These include helm, weapons, engineering, science and relay, which includes comms.

Scenarios are created by the game master, not unlike a D&D game, with the site providing a reference and various examples of how to go about this.

The free and open source game’s binaries can be obtained directly from the site, but it’s also available on Steam. The game isn’t limited to just Trek either, but scenarios can be crafted to fit whatever franchise or creative impulse feels right for that LAN party.

Obviously building the whole thing into a realistic starship bridge is optional, but it certainly looks like more fun that way.


hackaday.com/2025/03/23/build-…


“Unnecessary” Automation of a DIY Star Lamp Build


It all started with a gift idea: a star-field lamp in the form of a concrete sphere with lightpipes poking out where the stars are, lit up from the inside by LEDs. When you’re making one of these, maybe-just-maybe you’d be willing to drill a thousand holes and fit a thousand little plastic rods, but by the time you’re making a second, it’s time to build a machine to do the work for you.

So maybe we quibble with the channel name “Unnecessary Automation,” but we won’t quibble with the results. It’s a machine that orients a sphere, drills the hole, inserts the plastic wire, glues it together with a UV-curing glue, and then trims the end off. And if you like crazy machines, it’s a beauty.

The video goes through all of the design thoughts in detail, but it’s when it comes time to build the machine that the extra-clever bits emerge. For instance, [UA] used a custom 3D-printed peristaltic pump to push the glue out. Taking the disadvantage of peristaltic pumps – that they pulse – as an advantage, a custom housing was designed that dispensed the right amount between the rollers. The rolling glue dispenser mechanism tips up and back to prevent drips.

There are tons of other project-specific hacks here, from the form on the inside of the sphere that simplifies optic bundling and routing to the clever use of a razor blade as a spring. Give it a watch if you find yourself designing your own wacky machines. We think Rube Goldberg would approve. Check out this video for a more software-orientated take on fiber-optic displays.

youtube.com/embed/rHU8OqQk5KI?…

youtube.com/embed/3xhgEyMeA1I?…


hackaday.com/2025/03/23/unnece…


Hackaday Links: March 23, 2025


Hackaday Links Column Banner

What a long, strange trip it’s been for NASA astronauts Suni Williams and Bruce Wilmore, who finally completed their eight-day jaunt to space after 289 days. The duo returned to Earth from the ISS on Tuesday along with two other returning astronauts in a picture-perfect splashdown, complete with a dolphin-welcoming committee. For the benefit of those living under rocks these past nine months, Williams and Wilmore slipped the surly bonds way back in June on the first crewed test flight of the Boeing Starliner, bound for a short stay on the ISS before a planned return in the same spacecraft. Alas, all did not go to plan as their ride developed some mechanical difficulties on the way upstairs, and so rather than risk their lives on a return in a questionable capsule, NASA had them cool their heels for a couple of months while Starliner headed home without them.

There’s been a lot of talk about how Butch and Suni were “stranded,” but that doesn’t seem fair to us. Sure, their stay on the ISS was unplanned, or at least it wasn’t Plan A; we’re sure this is always a contingency NASA allows for when planning missions. Also unfortunate is the fact that they didn’t get paid overtime for the stay, not that you’d expect they would. But on the other hand, if you’re going to get stuck on a work trip, it might as well be at the world’s most exclusive and expensive resort.

Speaking of space, while it’s statistically unlikely that anyone reading this will ever get there, you can still get a little taste of what space travel is like if you’re willing to give up ten days of your life to lie in a waterbed. What’s more, the European Space Agency will pay you 5,000 euros to do it. The experiment is part of the ESA’s Vivaldi III campaign, an exploration of the effects of extended spaceflight on the human body. The “waterbed” thing is a little misleading, though; since the setup is designed to simulate the posture the body takes in microgravity, they use a tank of water (heated, we hope) with a waterproof cover to submerge volunteers up to their torso. This neutral body posture looks pretty comfortable if you’re sleeping in space, but we tend to think it’d get annoying pretty quickly down here. Especially for potty breaks, which aren’t done astronaut-style but rather by being transferred to a trolley which lets you do your business without breaking from the neutral posture. Still, 5,000 euros is 5,000 euros.

Bad news for the meme-making community, as it appears AI might be coming for you, too. A recent study found that LLMs like ChatGPT can meme better than humans, at least under certain conditions. To come to that conclusion, researchers used some pretty dank meme templates and pitted humans against ChatGPT-4o to come up with meme-worthy captions. They also had a different group of humans collaborate with the LLM to come up with meme captions, which for practical purposes probably means the humans let the chatbot do the heavy lifting and just filtered out the real stinkers. When they showed the memes to crowdsourced participants to rate them on humor, creativity, and shareability, they found that the LLM consistently produced memes that scored higher across all three categories. This makes sense when you think about it; the whole job of an LLM is to look at a bunch of words and come up with a consensus on what the next word should be. Happily, the funniest memes were written by humans, and the human-LLM collaborations were judged more creative and shareable. So we’ve got that going for us, which is good.

We noted the passing of quite a few surplus electronics shops in this space before, and the closing of each of them, understandable as they may, marks the end of an era. But we recently learned about one surplus outfit that’s still going strong. Best Electronics, which specializes in Atari retrocomputing, has been going strong for over 40 years, a neat trick when Atari itself went bankrupt over 30 years ago. While they appear to have a lot of new old stock bits and bobs — they’re said to have acquired “thousands and thousands” of pallets of Atari goods from their Sunnyvale warehouse when the company folded — they also claim to spend a lot of money on engineering development. Their online presence is delightfully Web 1.0, making it pretty hard to sort through, but we think that development is mainly upgraded PCBs for things like joysticks and keyboards. Whatever they’re doing, they should just keep on doing it.

And finally, have you ever seen a knitted breadboard? Now you have, and while it’s of no practical value, we still love it. Alanna Okun made it for the ITP Stupid Hackathon at NYU back in February. There aren’t any instructions or build docs, so it’s not clear how it works, but from the photos we’d guess there’s either conductive yarn or solid copper wire knitted into the pattern to serve as bus bars.


hackaday.com/2025/03/23/hackad…


RTL-SDR with Only a Browser


Surely by now you’ve at least heard of RTL-SDR — a software project that let’s cheap TV tuner dongles work as a software-defined radios. A number of projects and tools have spun off the original effort, but in his latest video, [Tech Minds] shows off a particularly unique take. It’s a Web browser-based radio application that uses WebUSB, so it doesn’t require the installation of any application software. You can see the program operating in the video below.

There are a few things you should know. First, you need the correct USB drivers for your RTL-SDR. Second, your browser must support WebUSB, of course. Practically, that means you need a Chromium-type browser. You may have to configure your system to allow raw access to the USB port, too.

Watching the video, you can see that it works quite well. According to the comments, it will work with a phone, too, which is an interesting idea. The actual Web application is available as open source. It isn’t going to compete with a full-fledged SDR program, but it looked surprisingly complete.

These devices have grown from a curiosity to a major part of radio hacking over the years. Firefox users can’t use WebUSB — well, not directly, anyway.

youtube.com/embed/INFu8jUHNhM?…


hackaday.com/2025/03/23/rtl-sd…


Building the Simplest Atomic Force Microscope


Doing it yourself may not get you the most precise lab equipment in the world, but it gets you a hands-on appreciation of the techniques that just can’t be beat. Today’s example of this adage: [Stoppi] built an atomic force microscope out of mostly junk parts and got pretty good results, considering. (Original is in German; read it translated here.)

The traditional AFM setup uses a piezo micromotor to raise and lower the sample into a very, very fine point. When this point deflects, it reads the height from the piezo setup and a motor stage moves on to the next point. Resolution is essentially limited by how fine a point you can make and how precisely you can read from the motion stages. Here, [stoppi]’s motion stage follows the traditional hacker avenue of twin DVD sleds, but instead of a piezo motor, he bounces a laser off of a mirror on top of the point and reads the deflection with a line sensor. It’s a clever and much simpler solution.

A lot of the learnings here are in the machine build. Custom nichrome and tungsten tips are abandoned in favor of a presumably steel compass tip. The first-draft spring ended up wobbling in the X and Y directions, rather than just moving in the desired Z, so that mechanism got reinforced with aluminum blocks. And finally, the line sensors were easily swamped by the laser’s brightness, so neutral density filters were added to the project.

The result? A nice side effect of the laser-bouncing-off-of-mirror setup is that the minimum resolvable height can be increased simply by moving the line sensors further and further away from the sample, multiplying the deflection by the baseline. Across his kitchen, [stoppi] is easily able to resolve the 35-um height of a PCB’s copper pour. Not bad for junk bin parts, a point from a crafts store, and a line sensor.

If you want to know how far you can push a home AFM project, check out [Dan Berard]’s absolutely classic hack. And once you have microscope images of every individual atom in the house, you’ll, of course, want to print them out.


hackaday.com/2025/03/23/buildi…


The Mysterious Mindscape Music Board


Sound cards on PC-compatible computer systems have a rather involved and convoluted history, with not only a wide diversity of proprietary standards, but also a collection of sound cards that were never advertised as such. Case in point the 1985 Mindscape Music Board, which was an add-on ISA card that came bundled with [Glen Clancy]’s Bank Street Music Writer software for IBM PC. This contrasted with the Commodore 64 version which used the Commodore SID sound chip. Recently both [Tales of Weird Stuff] and [The Oldskool PC] on YouTube both decided to cover this very rare soundcard.

Based around two General Instruments AY-3-8913 programmable sound generators, it enabled the output of six voices, mapped to six instruments in the Bank Street Music Writer software. Outside of this use this card saw no use, however, and it would fade into obscurity along with the software that it was originally bundled with. Only four cards are said to still exist, with [Tales of Weird Stuff] getting their grubby mitts on one.

As a rare slice of history, it is good to see this particular card getting some more love and attention, as it was, and still is, quite capable. [The Oldskool PC] notes that because the GI chip used is well-known and used everywhere, adding support for it in software and emulators is trivial, and efforts to reproduce the board are already underway.

Top image: Mindscape Music Board (Credit: Ian Romanick)

youtube.com/embed/Eeo4INoGyRY?…

youtube.com/embed/6fSpnIUDpeY?…


hackaday.com/2025/03/23/the-my…


22 siti hackerati, la risposta di Anonymous Italia agli attacchi DDoS di NoName057(16)


In risposta agli attacchi informatici lanciati ieri dagli hacktivisti filorussi di NoName057(16), il collettivo italiano Anonymous Italiaha reagito con ben 22 defacement mirati contro obiettivi russi tra la giornata del 21 e il 23 di Marzo.

Negli ultimi mesi, il panorama dell’hacktivismo cibernetico è stato caratterizzato da una continua escalation di attacchi e ritorsioni, con NoName057(16) che ha più volte preso di mira l’Italia, colpendo anche infrastrutture e istituzioni governative.

Questa volta, Anonymous Italia ha risposto colpendo diversi siti russi, utilizzando la tecnica del “deface” per alterare le pagine web e lanciare un chiaro messaggio ai loro avversari digitali. Per dimostrare la compromissione dei siti web attaccati, Anonymous Italia ha fatto riferimento alla Wayback Machine, uno strumento di archivio digitale che consente di visualizzare versioni precedenti di pagine web nel tempo.

Mostrando le istantanee dei siti prima e dopo l’attacco, il collettivo ha fornito prove concrete della violazione, evidenziando le modifiche apportate e i messaggi lasciati dagli hacktivisti. Alcuni di questi siti, nel frattempo, sono stati ripristinati, ma l’archivio della Wayback Machine conserva traccia dell’attacco, rendendo la compromissione verificabile anche a distanza di tempo.
Un esempio dell’uso della wayback machine per dimostrare l’effettiva compromissione del sito web

Defacement vs DDoS: Due Tecniche a Confronto


Nel panorama dell’hacktivismo cibernetico, le tecniche di attacco utilizzate dai gruppi hacker variano in base agli obiettivi e alle strategie adottate.

Due delle metodologie più diffuse sono il defacement e gli attacchi Distributed Denial-of-Service (DDoS), strumenti con finalità differenti ma entrambi capaci di generare impatti significativi sulle infrastrutture digitali. Mentre il defacement mira a modificare il contenuto di un sito web per trasmettere un messaggio politico o ideologico, il DDoS ha lo scopo di sovraccaricare un servizio online fino a renderlo inaccessibile.

Negli scontri tra hacktivisti, queste due tecniche sono state ampiamente utilizzate per colpire obiettivi avversari. Ad esempio Anonymous Italia preferisce il defacement, alterando i siti per diffondere specifici contenuti di interesse politico. Altri hacktivisti (come i filorussi di NoName057(16) o Killnet) hanno adottato il DDoS per colpire siti governativi e infrastrutture critiche causando disservizi temporanei.

La tecnica del Deface


Il defacement è una tecnica di attacco informatico in cui un aggressore modifica il contenuto di un sito web senza autorizzazione, sostituendo le pagine originali con messaggi politici, propaganda o semplici segni distintivi della propria attività. Questo tipo di attacco viene spesso utilizzato da gruppi hacktivisti per diffondere messaggi ideologici o da cyber criminali per danneggiare la reputazione di un’organizzazione.♦

Tuttavia, il defacement non è solo una questione di immagine: per poter alterare il contenuto di un sito, l’attaccante deve prima comprometterne la sua sicurezza. Questo avviene generalmente attraverso due metodi principali:

  • Accesso con credenziali amministrative rubate o deboli – Gli hacker potrebbero ottenere le credenziali di accesso attraverso phishing, log di infostealer, canali telegram, credenziali predefinite mai cambiate o attacchi di forza bruta. Una volta ottenuto l’accesso, possono alterare le pagine del sito con estrema facilità
  • Sfruttamento di vulnerabilità del software – Alcuni attacchi di defacement avvengono tramite Remote Code Execution (RCE) o altre vulnerabilità critiche nei CMS (Content Management System) o nei server web. Se il software della piattaforma non è aggiornato o presenta falle di sicurezza, un attaccante può eseguire comandi arbitrari sul sistema e modificare i file del sito.

Quando un sito subisce un defacement, è fondamentale non limitarsi a ripristinare il contenuto originale, ma avviare un’operazione di Incident Response per comprendere l’entità dell’attacco. L’attaccante potrebbe aver effettuato movimenti laterali all’interno della rete, compromettendo dati e sistemi collegati.

Hacktivismo cibernetico e legge


Come abbiamo visto, l’hacktivismo cibernetico rappresenta l’unione tra hacking e attivismo politico o sociale, utilizzando strumenti digitali per promuovere cause, denunciare ingiustizie o opporsi a governi e aziende. Gli hacktivisti impiegano tecniche di attacco informatico per attirare l’attenzione pubblica su questioni etiche, politiche o ambientali. Tuttavia, nonostante l’intento possa essere mosso da ideali di giustizia, queste azioni si scontrano spesso con le normative vigenti, che le considerano alla stregua di atti di criminalità informatica.

Mentre alcuni Stati tollerano certe forme di attivismo digitale se non causano danni diretti, la maggior parte delle legislazioni equipara gli attacchi informatici a crimini gravi, punibili con pene severe. Norme come il Computer Fraud and Abuse Act (CFAA) negli Stati Uniti o il Regolamento Generale sulla Protezione dei Dati (GDPR) in Europa vengono spesso usate per perseguire gli hacktivisti, anche quando le loro azioni mirano a esporre violazioni dei diritti umani o corruzione.

L’equilibrio tra sicurezza nazionale, libertà di espressione e diritto all’informazione è al centro delle discussioni legali sull’hacktivismo. Mentre alcuni lo vedono come una forma di protesta legittima nell’era digitale, altri lo considerano una minaccia alla stabilità informatica e alla privacy. La sfida per i legislatori è definire confini chiari tra atti di dissenso digitale e crimini informatici, garantendo che la repressione dell’hacktivismo non diventi un pretesto per limitare la libertà di espressione e il diritto all’accesso alle informazioni.

L'articolo 22 siti hackerati, la risposta di Anonymous Italia agli attacchi DDoS di NoName057(16) proviene da il blog della sicurezza informatica.


Booting a Desktop PDP-11


Ever heard of VENIX? There were lots of variants of Unix back in the day, and VENIX was one for the DEC Professional 380, which was — sort of — a PDP 11. The 1982 machine normally ran the unfortunately (but perhaps aptly) named P/OS, but you could get VENIX, too. [OldVCR] wanted to put one of these back online and decided the ST-506 hard drive was too risky. A solid-state drive upgrade and doubling the RAM to a whole megabyte was the plan.

It might seem funny to think of a desktop workstation that was essentially a PDP-11 minicomputer, but in the rush to corner the personal computer market, many vendors did the same thing: shrinking their legacy CPUs. DEC had a spotty history with small computers. [Ken Olsen] didn’t think anyone would ever want a personal computer, and the salespeople feared that cheap computers would eat into traditional sales. The Professional 350 was born out of DEC’s efforts to catch up, as [OldVCR] explains. He grabbed this one from a storage unit about to be emptied for scrap.

The post is very long, but you get a lot of history and a great look inside this vintage machine. Of course, the PDP-11 couldn’t actually handle more than 64K without tricks and you’ll learn more about that towards the end of the post, too.

Just as a preview, the story has a happy ending, including a surprising expression of gratitude from the aging computer. DEC didn’t enjoy much success in the small computer arena, eventually being bought by Compaq, which, in turn, was bought by Dell. During their heyday, this would have been unthinkable.

The PDP/11 did have some success because it was put on a chip that ended up in several lower-end machines, like the Heathkit H11. Ever wonder how people programmed the PDP computers with switches and lights?


hackaday.com/2025/03/23/bootin…


Musings on a Good Parallel Computer


Until the late 1990s, the concept of a 3D accelerator card was something generally associated with high-end workstations. Video games and kin would run happily on the CPU in one’s desktop system, with later extensions like MMX, 3DNow!, SSE, etc. providing a significant performance boost for games that supported it. As 3D accelerator cards (colloquially called graphics processing unit, or GPU) became prevalent, they took over almost all SIMD vector tasks, but one thing which they’re not good at is being a general parallel computer. While working on a software project this really ticked [Raph Levien] off and inspired him to cover his grievances.

Although the interaction between CPUs and GPUs has become tighter over the decades, with PCIe in particular being a big improvement over AGP & PCI, GPUs are still terrible at running arbitrary computing tasks and PCIe links are still glacial compared to communication within the GPU & CPU dies. With the introduction of asynchronous graphic APIs this divide became even more intense. The proposal thus is to invert this relationship.

There’s precedent for this already, with Intel’s Larrabee and IBM’s Cell processor merging CPU and GPU characteristics on a single die, though both struggled with developing for such a new kind of architecture. Sony’s PlayStation 3 was forced to add a GPU due to these issues. There is also the DirectStorage API in DirectX which bypasses the CPU when loading assets from storage, effectively adding CPU features to GPUs.

As [Raph] notes, so-called AI accelerators also have these characteristics, with often multiple SIMD-capable, CPU-like cores. Maybe the future is Cell after all.


hackaday.com/2025/03/23/musing…


NoName057(16) è tornato! Nuova ondata di DDoS sulle infrastrutture italiane


Gli hacker di NoName057(16) riavviano le loro attività ostili contro diversi obiettivi italiani, attraverso attacchi di Distributed Denial-of-Service (DDoS). Ma Telegram è in costante moderazione dei loro contenuti e i filorussi sono costretti a cambiare canale in modo costante.

Questa volta a farne le spese sono il Ministero delle infrastrutture e dei trasporti, l’amministrazione del sistema portuale dell’Adriatico orientale, l’aeroporto di Linate e altri obiettivi italiani.

NoName057(16) è un gruppo di hacker che si è dichiarato a marzo del 2022 a supporto della Federazione Russa. Hanno rivendicato la responsabilità di attacchi informatici a paesi come l’Ucraina, gli Stati Uniti e altri vari paesi europei. Questi attacchi vengono in genere eseguiti su agenzie governative, media e siti Web di società private.

Che cos’è un attacco Distributed Denial of Service


Un attacco DDoS (Distributed Denial of Service) è un tipo di attacco informatico in cui vengono inviate una grande quantità di richieste a un server o a un sito web da molte macchine diverse contemporaneamente, al fine di sovraccaricare le risorse del server e renderlo inaccessibile ai suoi utenti legittimi.

Queste richieste possono essere inviate da un grande numero di dispositivi infetti da malware e controllati da un’organizzazione criminale, da una rete di computer compromessi chiamata botnet, o da altre fonti di traffico non legittime. L’obiettivo di un attacco DDoS è spesso quello di interrompere le attività online di un’organizzazione o di un’azienda, o di costringerla a pagare un riscatto per ripristinare l’accesso ai propri servizi online.

Gli attacchi DDoS possono causare danni significativi alle attività online di un’organizzazione, inclusi tempi di inattività prolungati, perdita di dati e danni reputazionali. Per proteggersi da questi attacchi, le organizzazioni possono adottare misure di sicurezza come la limitazione del traffico di rete proveniente da fonti sospette, l’utilizzo di servizi di protezione contro gli attacchi DDoS o la progettazione di sistemi resistenti agli attacchi DDoS.

Occorre precisare che gli attacchi di tipo DDoS, seppur provocano un disservizio temporaneo ai sistemi, non hanno impatti sulla Riservatezza e Integrità dei dati, ma solo sulla loro disponibilità. pertanto una volta concluso l’attacco DDoS, il sito riprende a funzionare esattamente come prima.

Che cos’è l’hacktivismo cibernetico


L’hacktivismo cibernetico è un movimento che si serve delle tecniche di hacking informatico per promuovere un messaggio politico o sociale. Gli hacktivisti usano le loro abilità informatiche per svolgere azioni online come l’accesso non autorizzato a siti web o a reti informatiche, la diffusione di informazioni riservate o il blocco dei servizi online di una determinata organizzazione.

L’obiettivo dell’hacktivismo cibernetico è di sensibilizzare l’opinione pubblica su questioni importanti come la libertà di espressione, la privacy, la libertà di accesso all’informazione o la lotta contro la censura online. Gli hacktivisti possono appartenere a gruppi organizzati o agire individualmente, ma in entrambi i casi utilizzano le loro competenze informatiche per creare un impatto sociale e politico.

È importante sottolineare che l’hacktivismo cibernetico non deve essere confuso con il cybercrime, ovvero la pratica di utilizzare le tecniche di hacking per scopi illeciti come il furto di dati personali o finanziari. Mentre il cybercrime è illegale, l’hacktivismo cibernetico può essere considerato legittimo se mira a portare all’attenzione pubblica questioni importanti e a favorire il dibattito democratico. Tuttavia, le azioni degli hacktivisti possono avere conseguenze legali e gli hacktivisti possono essere perseguiti per le loro azioni.

Chi sono gli hacktivisti di NoName057(16)


NoName057(16) è un gruppo di hacker che si è dichiarato a marzo del 2022 a supporto della Federazione Russa. Hanno rivendicato la responsabilità di attacchi informatici a paesi come l’Ucraina, gli Stati Uniti e altri vari paesi europei. Questi attacchi vengono in genere eseguiti su agenzie governative, media e siti Web di società private

Le informazioni sugli attacchi effettuati da NoName057(16) sono pubblicate nell’omonimo canale di messaggistica di Telegram. Secondo i media ucraini, il gruppo è anche coinvolto nell’invio di lettere di minaccia ai giornalisti ucraini. Gli hacker hanno guadagnato la loro popolarità durante una serie di massicci attacchi DDOS sui siti web lituani.

Le tecniche di attacco DDoS utilizzate dal gruppo sono miste, prediligendo la “Slow http attack”.

La tecnica del “Slow Http Attack”


L’attacco “Slow HTTP Attack” (l’articolo completo a questo link) è un tipo di attacco informatico che sfrutta una vulnerabilità dei server web. In questo tipo di attacco, l’attaccante invia molte richieste HTTP incomplete al server bersaglio, con lo scopo di tenere occupate le connessioni al server per un periodo prolungato e impedire l’accesso ai legittimi utenti del sito.

Nello specifico, l’attacco Slow HTTP sfrutta la modalità di funzionamento del protocollo HTTP, che prevede che una richiesta HTTP sia composta da tre parti: la richiesta, la risposta e il corpo del messaggio. L’attaccante invia molte richieste HTTP incomplete, in cui il corpo del messaggio viene inviato in modo molto lento o in modo incompleto, bloccando la connessione e impedendo al server di liberare le risorse necessarie per servire altre richieste.

Questo tipo di attacco è particolarmente difficile da rilevare e mitigare, poiché le richieste sembrano legittime, ma richiedono un tempo eccessivo per essere elaborate dal server. Gli attacchi Slow HTTP possono causare tempi di risposta molto lenti o tempi di inattività del server, rendendo impossibile l’accesso ai servizi online ospitati su quel sistema.

Per proteggersi da questi attacchi, le organizzazioni possono implementare soluzioni di sicurezza come l’uso di firewall applicativi (web application firewall o WAF), la limitazione delle connessioni al server e l’utilizzo di sistemi di rilevamento e mitigazione degli attacchi DDoS

L'articolo NoName057(16) è tornato! Nuova ondata di DDoS sulle infrastrutture italiane proviene da il blog della sicurezza informatica.


Piezo Sensor Reviewed


If you do FDM 3D printing, you know one of the biggest problems is sensing the bed. Nearly all printers have some kind of bed probing now, and it makes printing much easier, but there are many different schemes for figuring out where the bed is relative to the head. [ModBot] had a Voron with a clicky probe but wanted to reclaim the space it used for other purposes. In the video, also linked below, he reviews the E3D PZ probe which is a piezoelectric washer, and the associated electronics to sense your nozzle crashing into your print bed.

There are many options, and it seems like each has its pros and cons. We do like solutions that actually figure out where the tip is so you don’t have to mess with offsets as you do with probes that measure from a probe tip instead of the print head.

Of course, there are other piezo probes we’ve seen. There are also many other kinds of sensors available. The version from E3D is available as a kit you can add to anything, assuming you can figure out how. Or you can do like [ModBot] did and opt for an E3D heatsink with the washer already in place which, presumably, will best fit E3D products.

From the printer’s point of view, the device looks like a normal end stop, so it is simple to configure the printer. There are other ways to sense a head crash, of course. We keep meaning to install one of the “real time” sensors you can get now, but our CR Touch works well enough that we never find the time.

youtube.com/embed/6b8DWEpVo74?…


hackaday.com/2025/03/22/piezo-…


Twisting Magnetism to Control Electron Flow


Microscopic view of chiral magnetic material

If you ever wished electrons would just behave, this one’s for you. A team from Tohoku, Osaka, and Manchester Universities has cracked open an interesting phenomenon in the chiral helimagnet α-EuP3: they’ve induced one-way electron flow without bringing diodes into play. Their findings are published in the Proceedings of the National Academy of Sciences.

The twist in this is quite literal. By coaxing europium atoms into a chiral magnetic spiral, the researchers found they could generate rectification: current that prefers one direction over another. Think of it as adding a one-way street in your circuit, but based on magnetic chirality rather than semiconductors. When the material flips to an achiral (ferromagnetic) state, the one-way effect vanishes. No asymmetry, no preferential flow. They’ve essentially toggled the electron highway signs with an external magnetic field. This elegant control over band asymmetry might lead to low-power, high-speed data storage based on magnetic chirality.

If you are curious how all this ties back to quantum theory, you can trace the roots of chiral electron flow back to the early days of quantum electrodynamics – when physicists first started untangling how particles and fields really interact.

There’s a whole world of weird physics waiting for us. In the field of chemistry, chirality has been covered by Hackaday, foreshadowing the lesser favorable ways of use. Read up on the article and share with us what you think.


hackaday.com/2025/03/22/twisti…


Generative Art Machine Does it One Euro at a Time


[Niklas Roy] obviously had a great time building this generative art cabinet that puts you in the role of the curator – ever-changing images show on the screen, but it’s only when you put your money in that it prints yours out, stamps it for authenticity, and cuts it off the paper roll with a mechanical box cutter.

If you like fun machines, you should absolutely go check out the video (embedded below without resorting to YouTube!). The LCD screen has been stripped of its backlight, allowing you to verify that the plot exactly matches the screen by staring through it. The screen flashes red for a sec, and your art is then dispensed. It’s lovely mechatronic theater. We also dig the “progress bar” that is represented by how much of your one Euro’s worth of art it has plotted so far. And it seems to track perfectly; Bill Gates could learn something from watching this. Be sure to check out the build log to see how it all came together.

You’d be forgiven if you expected some AI to be behind the scenes these days, but the algorithm is custom designed by [Niklas] himself, ironically adding to the sense of humanity behind it all. It takes the Unix epoch timestamp as the seed to generate a whole bunch of points, then it connects them together. Each piece is unique, but of course it’s also reproducible, given the timestamp. We’re not sure where this all lies in the current debates about authenticity and ownership of art, but that’s for the comment section.

If you want to see more of [Niklas]’s work, well this isn’t the first time his contraptions have graced our pages. But just last weekend at Hackaday Europe was the first time that he’s ever given us a talk, and it’s entertaining and beautiful. Go check that out next.

hackaday.com/wp-content/upload…


hackaday.com/2025/03/22/genera…


Allarme sicurezza: i dati di Smart-Cash.it nelle mani degli hacker!


Recentemente, Smart-Cash.it, una community internazionale che coinvolge imprese commerciali, imprese di produzione e consumatori, è stata vittima di una grave violazione dei dati. Un utente su BreachForums, nicknameSorb, ha pubblicato un annuncio per la vendita di un database contenente informazioni sensibili degli utenti di Smart-Cash.it. Questo articolo esplora i dettagli della violazione, le motivazioni del malintenzionato e le misure di sicurezza che le aziende dovrebbero adottare per prevenire tali incidenti.

Cos’è Smart-Cash.it? Smart-Cash.it è una piattaforma che mira a aumentare la visibilità delle imprese e a far risparmiare i consumatori attraverso i buoni CBK. Le imprese che aderiscono al circuito rilasciano buoni CBK ai clienti, calcolati in percentuale sull’importo speso. Ogni impresa può decidere l’importo del buono da rilasciare in base alle proprie esigenze commerciali.

Dettagli della violazione dei dati Sorb, ha ottenuto un dump del database MySQL di Smart-Cash.it in formato CSV, contenente 197 tabelle. I dati includono informazioni sui clienti, hash delle password, accumuli di cashback, transazioni, codici regalo e altro. inoltre ha pubblicato esempi di hash delle password e campioni di dati JSON che includono nomi, email, indirizzi IP, codici PIN, numeri di carta e altro.

Esempi di dati compromessi

  • Hash delle password: Esempi di hash delle password sono stati forniti, indicando che le password degli utenti sono state compromesse.
  • Dati personali: Un campione di dati JSON include nomi, email, indirizzi IP, codici PIN, numeri di carta e altro.
  • Transazioni: Esempi di transazioni mostrano dettagli come il saldo, il tipo di transazione, l’importo e le commissioni.
  • Esempio di dati JS

Il criminal hacker ha messo in vendita il database compromesso di Smart-Cash.it per 500$, offrendo la possibilità di contattarlo tramite messaggio privato o Telegram. Sorb non ha esitato a deridere stonewall.capital, affermando che, sebbene i loro prodotti siano validi, le loro pratiche di sicurezza informatica lasciano molto a desiderare.

Implicazioni per gli utenti La violazione dei dati di Smart-Cash.it ha esposto circa 127,000 utenti al rischio di furto d’identità e frode finanziaria. Le informazioni compromesse includono nomi completi, indirizzi email, indirizzi IP, codici PIN e numeri di carta, rendendo gli utenti vulnerabili a vari tipi di attacchi. Questo incidente sottolinea l’importanza di proteggere i dati personali e di adottare misure di sicurezza adeguate.

Questo attacco sottolinea l’importanza di migliorare la sicurezza dei database. È fondamentale che i database siano configurati in modo sicuro, regolarmente aggiornati e monitorati per rilevare accessi non autorizzati. Implementare la crittografia per i dati sensibili e utilizzare controlli di accesso robusti può aiutare a mitigare i rischi. Inoltre, vanno effettuati audit di sicurezza regolarmente e valutazioni delle vulnerabilità per identificare e risolvere potenziali debolezze. Utilizzare test di penetrazione può anche aiutare a simulare potenziali attacchi e migliorare i meccanismi di difesa.

Questo dataleak solleva importanti questioni sulla sicurezza informatica e la protezione dei dati personali. Le aziende devono adottare misure rigorose per proteggere le informazioni dei clienti e prevenire futuri incidenti di sicurezza. La facilità con cui concediamo i nostri dati a terze parti può ritorcersi contro, come dimostra questo caso, mettendo a rischio la nostra identità e sicurezza finanziaria. In particolar modo quando parliamo di questioni finanziarie, chi gestisce questi dati deve adottare standard elevati e, sottolineo, audit continui.

L'articolo Allarme sicurezza: i dati di Smart-Cash.it nelle mani degli hacker! proviene da il blog della sicurezza informatica.


Card Radios Remembered


We know how [Techmoan] feels. In the 1980s we had a bewildering array of oddball gadgets and exciting new tech. But as kids we didn’t have money to buy a lot of what we saw. But he had a £5 note burning a hole in his pocket from Christmas and found a Casio RD-10 “card radio” on sale and grabbed it. He’s long-ago lost that one, but he was able to find a new old stock one and shows us the little gadget in the video below.

The card-thin (1.9 mm) FM radio had many odd features, especially for the 1980s. For one thing, it took a coin cell, which was exotic in those days. The headphones had a special flat connector that reminded us of an automotive fuse. Even the idea of an earbud was odd at that time.

It was a good idea not to lose the earbud, as it had that strange connector. The earbud worked as the antenna and power switch, too. Oddly enough, you could get a slightly fatter AM radio version, and they even made one that was AM and FM. Unsurprisingly, Casio even made a version with a calculator built-in. It had a solar cell, but that only powers the calculator. You still needed the coin cell for the radio.

The sound? Meh. But what did you expect? There was a stereo version, too. However, that one had a rechargeable battery, which was not in good health after a few decades. He also shows a Sony card radio that is a bit different. We were hoping for a teardown, especially of the rechargeable since it was toast, anyway, but for now, we’ll have to imagine what’s inside.

We love nostalgic radios, although usually they are a little older. We miss the days when a kid might think it was cool to see an ad touting: “Oh boy! We’re radio engineers!”

youtube.com/embed/AqMGMZjAKZw?…


hackaday.com/2025/03/22/card-r…


Oracle è stata Violata? Il giallo della compromissione di 140.000 tenant Cloud


Nella serata di ieri, 21 marzo 2025, durante una delle consuete esplorazioni nel sottobosco del web di DarkLab, ci siamo inbattuti in una notizia che potrebbe far tremare i polsi a molti amministratori IT: un presunto attacco alla Oracle Cloud.

Da quanto riportato successivamente da CloudSek, sembrerebbe che ci sia stata l’esfiltrazione presunta di 6 milioni di record, coinvolgendo oltre 140.000 tenant. Un grande bottino di informazioni qualora queste confermate da Oracle.

Disclaimer: Questo rapporto include screenshot e/o testo tratti da fonti pubblicamente accessibili. Le informazioni fornite hanno esclusivamente finalità di intelligence sulle minacce e di sensibilizzazione sui rischi di cybersecurity. Red Hot Cyber condanna qualsiasi accesso non autorizzato, diffusione impropria o utilizzo illecito di tali dati. Al momento, non è possibile verificare in modo indipendente l’autenticità delle informazioni riportate, poiché l’organizzazione coinvolta non ha ancora rilasciato un comunicato ufficiale sul proprio sito web. Di conseguenza, questo articolo deve essere considerato esclusivamente a scopo informativo e di intelligence.

La pubblicazione si Breach Forums


Il tutto è partito da un post su un forum underground, dove un utente con lo pseudonimo “rose87168” ha dichiarato di aver violato l’endpoint di login della Oracle Cloud (login.(region-name).oraclecloud.com), ottenendo accesso a dati sensibili come file JKS, password SSO criptate, file chiave e chiavi JPS dell’enterprise manager.

Non contento, il nostro “amico” ha messo in vendita questi 6 milioni di record, offrendo persino incentivi a chi lo aiutasse a decriptare le password SSO o a craccare quelle LDAP.

Oracle, dal canto suo, ha prontamente smentito qualsiasi violazione. In una dichiarazione rilasciata a BleepingComputer, l’azienda ha affermato: “Non c’è stata alcuna violazione di Oracle Cloud. Le credenziali pubblicate non appartengono a Oracle Cloud. Nessun cliente di Oracle Cloud ha subito una violazione o ha perso dati.”

Tuttavia, alcune analisi indipendenti sembrerebbero suggerire il contrario. Ad esempio, Kudelski Security ha riportato che il threat actor ha condiviso URL dell’Internet Archive come prova del suo accesso ai server Oracle Cloud, caricando un file .txt contenente il suo indirizzo email su login.us2.oraclecloud.com.

Inoltre, su Reddit, nella community r/blueteamsec, diversi utenti hanno discusso dell’incidente, sottolineando come potrebbe aver coinvolto le tradizionali login OCI, ma non l’IDCS, suggerendo di ruotare le credenziali il prima possibile.

Cosa è importante fare ora


In attesa di ulteriori conferme o smentite, è consigliabile per tutti gli amministratori e i responsabili della sicurezza:

  • Monitorare attentamente i propri sistemi per attività sospette.
  • Aggiornare regolarmente le password e implementare l’autenticazione multi-fattore (MFA).
  • Verificare se le proprie credenziali sono state compromesse utilizzando strumenti come quelli messi a disposizione da CloudSEK.

Ricordiamoci sempre che, in un mondo digitale in continua evoluzione, la prudenza non è mai troppa.

L'articolo Oracle è stata Violata? Il giallo della compromissione di 140.000 tenant Cloud proviene da il blog della sicurezza informatica.


Acoustic Levitation Gets Insects Ready For Their Close-Up


The average Hackaday reader is likely at least familiar with acoustic levitation — a technique by which carefully arranged ultrasonic transducers can be used to suspend an object in the air indefinitely. It’s a neat trick, the sort of thing that drives them wild at science fairs, but as the technique only works on exceptionally small and light objects it would seem to have little practical use.

That is, unless, you happen to be interested in exceptionally small and light objects. A paper titled Automated Photogrammetric Close-Range Imaging System for Small Invertebrates Using Acoustic Levitation describes a fascinating device which allows the researchers to image insects in what’s essentially a weightless environment.

With the delicate specimens suspended in front of the lens, there’s no background to worry about and they can be perfectly lit from all angles. What’s more, with careful control of the ultrasonic transducers, it’s possible to control the rotation of the target — allowing researchers to produce 3D scans of the insects using just one camera.

There isn’t a whole lot of technical detail on the device itself, other than the fact that spherical chamber has a radius of 60 mm and is fitted with 96 Murata MA40S4R/S transducers operating at 40 kHz. The paper notes that early attempts to control the transducer array with a Arduino Mega failed, and that the team had to switch over to a FPGA. With their current signal generator stage, the researchers are able to rotate the specimen by 5° angles.

Interested in learning more about acoustic levitation? University of Bristol research scientist Asier Marzo gave a talk on the subject at Hackaday Belgrade in 2018 that you won’t want to miss.


hackaday.com/2025/03/22/acoust…


Thanks for Hackaday Europe!


We just got back from Hackaday Europe last weekend, and we’re still coming down off the high. It was great to be surrounded by so many crazy, bright, and crazy-bright folks all sharing what they are pouring their creative energy into. The talks were great, and the discussions and impromptu collaborations have added dramatically to our stack of to-do projects. (Thanks?) Badges were hacked, stories were shared, and a good time was had by all.

At the event, we were approached by someone who wanted to know if we could replicate something like Hackaday Europe in a different location, one where there just isn’t as vibrant a hacking scene. And the answer, of course, was maybe, but probably not.

It’s not that we don’t try to put on a good show, bring along fun schwag, and schedule up a nice location. But it’s the crowd of people who attend who make a Hackaday event a Hackaday event. Without you all, it just wouldn’t work.

So in that spirit, thanks to everyone who attended, and who brought along their passions and projects! It was great to see you all, and we’ll do it again soon.

This article is part of the Hackaday.com newsletter, delivered every seven days for each of the last 200+ weeks. It also includes our favorite articles from the last seven days that you can see on the web version of the newsletter. Want this type of article to hit your inbox every Friday morning? You should sign up!


hackaday.com/2025/03/22/thanks…


The Fastest MS-DOS Gaming PC Ever


After [Andy]’s discovery of an old ISA soundcard at his parents’ place that once was inside the family PC, the onset of a wave of nostalgia for those old-school sounds drove him off the deep end. This is how we get [Andy] building the fastest MS-DOS gaming system ever, with ISA slot and full hardware compatibility. After some digging around, the fastest CPU for an Intel platform that still retained ISA compatibility turned out to be Intel’s 4th generation Core series i7-4790K CPU, along with an H81 chipset-based MiniITX mainboard.

Of note is that ISA slots on these newer boards are basically unheard of outside of niche industrial applications, ergo [Andy] had to tap into the LPC (low pin count) debug port & hunt down the LDRQ signal on the mainboard. LPC is a very compact version of a PCI bus, that works great with ISA adapter boards, specially an LPC to ISA adapter like [Andy]’s dISAppointment board as used here.

A PCIe graphics card (NVidia 7600 GT, 256 MB VRAM), ISA soundcard, dodgy PSU and a SATA SSD were added into a period-correct case. After this Windows 98 was installed from a USB stick within a minute using [Eric Voirin]’s Windows 98 Quick Install. This gave access to MS-DOS and enabled the first tests, followed by benchmarking.

Benchmarking MS-DOS on a system this fast turned out to be somewhat messy with puzzling results. The reason for this was that the BIOS default settings under MS-DOS limited the CPU to non-turbo speeds. After this the system turned out to be actually really quite fast at MS-DOS (and Windows 98) games, to nobody’s surprise.

If you’d like to run MS-DOS on relatively modern hardware with a little less effort, you could always pick up a second-hand ThinkPad and rip through some Descent.

youtube.com/embed/7LIPTQjQAPE?…


hackaday.com/2025/03/22/the-fa…


Telegram nel mirino! Broker Zero-Day ricercano RCE per un prezzo modico di 4 milioni di dollari


Con la sua base utenti che supera il miliardo di persone, in particolare in Russia e Ucraina, Telegram è un obiettivo di grande valore per gli attori legati allo Stato. Gli esperti di sicurezza, notano da tempo che la crittografia di Telegram è in ritardo rispetto a Signal e WhatsApp.

Ad esempio le chat predefinite non hanno protezione end-to-end di default e utilizzano protocolli non verificati.

Problemi passati su Telegram


I meccanismi di crittografia e gestione dei file di Telegram sono stati sottoposti a ripetuti controlli:

  • Android: uno zero-day “EvilVideo” del luglio 2024 ha consentito agli aggressori di camuffare APK dannosi come video, sfruttando la funzionalità di download automatico di Telegram. Patchato nella versione 10.14.5, il difetto richiedeva l’interazione dell’utente ma evidenziava rischi nelle impostazioni predefinite.
  • Windows: una vulnerabilità basata su un errore del 2024 (etichettatura errata dei file “.pyzw”) ha consentito l’esecuzione di script Python, in seguito mitigata aggiungendo “.untrusted” ai file sospetti.
  • Problemi storici: tra i difetti passati c’è un exploit Unicode del 2017 che consente la distribuzione di malware di cryptomining tramite file mascherati.

Fonti del settore suggeriscono che questi prezzi potrebbero essere inferiori a quelli di mercato, poiché i broker spesso rivendono gli exploit ai governi a costi di acquisizione pari a 2-3 volte superiori.

La ricerca di nuovi zero day per telegram


Una società russa di intermediazione di exploit (broker zeroday), di nome Operation Zero, ha annunciato pubblicamente ricompense fino a 4 milioni di dollari per le vulnerabilità zero-day in Telegram, a dimostrazione del crescente interesse da parte degli Stati nel compromettere la popolare app di messaggistica.
Post pubblicato su X da Operation0 che mostra i bug di sicurezza messi in vendita per telegram
Il modello del bug bounty program di Operation Zero include:

  • RCE con un clic → fino a 500.000 dollari
  • RCE senza clic → fino a 1,5 milioni di dollari
  • Sfruttamento dell’intera catena (full-chain) → fino a 4 milioni di dollari

La categoria “full-chain” si riferisce agli exploit multifase che garantiscono l’accesso al sistema operativo di un dispositivo dopo la compromissione iniziale di Telegram.

L’azienda, che serve esclusivamente il governo russo e le entità locali, sta cercando exploit di esecuzione di codice remoto (RCE) nelle versioni Android, iOS e Windows di Telegram. I pagamenti sono scalabili in base alla sofisticatezza dell’exploit.

Chi sono i broker zero-day?


I broker zero-day sono intermediari specializzati nell’acquisto e nella vendita di exploit per vulnerabilità informatiche sconosciute ai vendor del software. Queste falle, dette “zero-day” perché non ancora corrette, vengono scoperte da ricercatori indipendenti, hacker o gruppi di sicurezza e possono valere milioni di dollari a seconda della loro criticità. I broker operano come mercati paralleli della cybersicurezza, offrendo exploit sia a governi e agenzie di intelligence che a gruppi criminali e aziende di sicurezza privata.

Il mercato degli zero-day è diviso in due categorie principali: il “mercato bianco”, dove aziende di cybersecurity come Zerodium o Trend Micro acquistano vulnerabilità per scopi di ricerca e protezione, e il “mercato grigio/nero”, in cui broker più riservati, come Operation Zero, vendono exploit a governi o enti che potrebbero usarli per attività di sorveglianza, attacchi mirati o cyber warfare. L’anonimato e la segretezza sono fondamentali in questo settore, poiché la divulgazione di un exploit riduce immediatamente il suo valore.

L'articolo Telegram nel mirino! Broker Zero-Day ricercano RCE per un prezzo modico di 4 milioni di dollari proviene da il blog della sicurezza informatica.


Iran sotto attacco cyber: 116 navi bloccate e comunicazioni distrutte. Settimane per recuperare


C’è stato un grave attacco informatico la sera del 17 marzo che ha interrotto il sistema di comunicazione delle più grandi compagnie di navigazione iraniane contemporaneamente. La responsabilità dell’operazione è stata rivendicata dal gruppo Lab Dookhtegan, che in precedenza aveva compiuto azioni contro le infrastrutture strategiche del Paese. Questa volta l’obiettivo è stato le navi associate alle esportazioni di petrolio e dell’industria militare.

Le società iraniane NITC e IRISL, attori chiave del trasporto marittimo della regione e soggette a sanzioni da parte di Stati Uniti, Regno Unito e Unione Europea, sono state attaccate. Fin dalle prime ore del mattino del 18 marzo, gli equipaggi di queste navi sono rimasti isolati gli uni dagli altri, incapaci di comunicare anche in situazioni di emergenza. Anche i collegamenti con i porti e le infrastrutture logistiche globali sono stati interrotti, causando interruzioni nelle forniture. Gli esperti ritengono che il completo ripristino delle comunicazioni potrebbe richiedere diverse settimane.
Informativa inviata dal gruppo hacker LabDookhtegan su Twitter
Secondo i dati preliminari, gli hacker sono riusciti a penetrare nei sistemi di comunicazione satellitare delle navi, ad accedere alle apparecchiature del server ed eseguire comandi che hanno distrutto dati critici. Di conseguenza, i centri di archiviazione delle informazioni sono stati chiusi e parte dell’infrastruttura digitale è stata danneggiata in modo irreversibile.

L’attacco è considerato uno dei più grandi all’industria marittima iraniana degli ultimi anni. Ha inferto un duro colpo non solo alla logistica delle spedizioni, ma anche ai legami economici di un Paese dipendente dalle esportazioni marittime. Particolarmente vulnerabili sono i soggetti sottoposti a sanzioni internazionali, che limitano la loro capacità di proteggersi dagli attacchi informatici e di interagire con partner esterni.

Le autorità iraniane non hanno ancora commentato l’incidente, ma gli esperti stanno discutendo della possibilità di ulteriori attacchi, soprattutto considerando le vulnerabilità dei sistemi satellitari e di navigazione. Particolarmente preoccupante è il fatto che alcune navi si trovassero in acque internazionali al momento dell’attacco.

Data la portata dell’intrusione, l’incidente potrebbe indurre a riconsiderare gli standard di sicurezza nel settore marittimo, in particolare in termini di protezione crittografica e isolamento dei principali nodi di comunicazione. Viene inoltre discussa la necessità di una risposta rapida a tali minacce, anche attraverso la creazione di canali di comunicazione di backup e scenari di resilienza informatica.

Il gruppo Lab Dookhtegan ha già dichiarato di considerare tali attacchi come uno strumento per esercitare pressione sulle catene logistiche e militari iraniane. Pertanto, il cyberspazio sta diventando sempre più un’arena per la lotta per l’influenza nelle aree di conflitto internazionale.

L'articolo Iran sotto attacco cyber: 116 navi bloccate e comunicazioni distrutte. Settimane per recuperare proviene da il blog della sicurezza informatica.


Biosynthesis of Polyester Amides in Engineered Escherichia Coli


Polymers are one of the most important elements of modern-day society, particularly in the form of plastics. Unfortunately most common polymers are derived from fossil resources, which not only makes them a finite resource, but is also problematic from a pollution perspective. A potential alternative being researched is that of biopolymers, in particular those produced by microorganisms such as everyone’s favorite bacterium Escherichia coli (E. coli).

These bacteria were the subject of a recent biopolymer study by [Tong Un Chae] et al., as published in Nature Chemical Biology (paywalled, break-down on Arstechnica).

By genetically engineering E. coli bacteria to use one of their survival energy storage pathways instead for synthesizing long chains of polyester amides (PEAs), the researchers were able to make the bacteria create long chains of mostly pure PEA. A complication here is that this modified pathway is not exactly picky about what amino acid monomers to stick onto the chain next, including metabolism products.

Although using genetically engineered bacteria for the synthesis of products on an industrial scale isn’t uncommon (see e.g. the synthesis of insulin), it would seem that biosynthesis of plastics using our prokaryotic friends isn’t quite ready yet to graduate from laboratory experiments.


hackaday.com/2025/03/22/biosyn…


A Cute Handheld Gaming Device That You Can Build In An Altoids Tin


The MintyPi was a popular project that put a Raspberry Pi inside an Altoids tin to make a pocketable gaming handheld. Unfortunately, it’s not the easiest build to replicate anymore, but [jackw01] was still a fan of the format. Thus was born the Pi Tin—a clamshell handheld for portable fun!
Neat, huh? More pocket-sized than the Game Boy Pocket.
The build is based around the Raspberry Pi Zero 2W, which packs more power than the original Pi Zero into the same compact form factor. It’s combined with a 320 x 240 TFT LCD screen and a 2000 mAh lithium-polymer battery which provides power on the go.

There are also a pair of custom PCBs used to lace everything together, including the action buttons, D-pad, and power management hardware. Depending on your tastes, you have two main enclosure options. You can use the neat 3D printed clamshell seen here in beautiful teal, or you can go with the classic Altoids tin build—just be careful when you’re cutting it to suit! Files can be found on GitHub for the curious.

We love a good handheld project around these parts; it’s particularly awesome how much gaming you can fit in your pocket given the magic of the Raspberry Pi and modern emulation. If you’re cooking up your own little retro rig, don’t hesitate to let us know!


hackaday.com/2025/03/21/a-cute…


Producing Syngas From CO2 and Sunlight With Direct Air Capture



The prototype DACCU device for producing syngas from air. (Credit: Sayan Kar, University of Cambridge)
There is more carbon dioxide (CO2) in the atmosphere these days than ever before in human history, and while it would be marvelous to use these carbon atoms for something more useful, capturing CO2 directly from the air isn’t that easy. After capturing it would also be great if you could do something more with it than stuff it into a big hole. Something like producing syngas (CO + H2) for example, as demonstrated by researchers at the University of Cambridge.

Among the improvements claimed in the paper as published in Nature Energy for this direct air capture and utilization (DACCU) approach are that it does not require pure CO2 feedstock, but will adsorb it directly from the air passing over a bed of solid silica-amine. After adsorption, the CO2 can be released again by exposure to concentrated light. Following this the conversion to syngas is accomplished by passing it over a second bed consisting of silica/alumina-titania-cobalt bis(terpyridine), that acts as a photocatalyst.

The envisioned usage scenario would be CO2 adsorption during the night, with concentrated solar power releasing it the day with subsequent production of syngas. Inlet air would be passed only over the adsorption section before switching the inlet off during the syngas generating phase. As a lab proof-of-concept it seems to work well, with outlet air stripped from virtually all CO2 and very high conversion ratio from CO2 to syngas.

Syngas has historically been used as a replacement for gasoline, but is also used as a source of hydrogen (e.g. steam reformation (SMR) of natural gas) where it’s used for reduction of iron ore, as well as the production of methanol as a precursor to many industrial processes. Whether this DACCU approach provides a viable alternative to SMR and other existing technologies will become clear once this technology moves from the lab into the real world.

Thanks to [Dan] for the tip.


hackaday.com/2025/03/21/produc…


Moving Software Down to Hardware


In theory, any piece of software could be built out of discrete pieces of hardware, provided there are enough transistors, passive components, and time available. In general, though, we’re much more likely to reach for a programmable computer or microcontroller for all but the simplest tasks for several reasons: cost, effort, complexity, economics, and sanity. [Igor Brichkov] was working with I2C and decided that he wanted to see just where this line between hardware and software should be by implementing this protocol itself directly with hardware.

One of the keys to “programming” a communications protocol in hardware is getting the timing right, the first part of which is initializing communications between this device and another on the bus. [Igor] is going to be building up the signal in parts and then ORing them together. The first part is a start condition, generated by one oscillator and a counter. This also creates a pause, at which point a second oscillator takes over and sends data out. The first data needed for I2C is an address, which is done with a shift register and a counter pre-set to send the correct bits out on the communications lines.

To build up the rest of the signal, including data from the rotary encoder [Igor] is using for his project, essentially sets of shift registers and counters are paired together to pass data out through the I2C communications lines in sequence. It could be thought of that the main loop of the hardware program is a counter, which steps through all the functions sequentially, sending out data from the shift registers one by one. We saw a similar project over a decade ago, but rather than automating the task of sending data on I2C it allowed the user to key in data manually instead.

youtube.com/embed/_pVlHPgud7I?…


hackaday.com/2025/03/21/moving…


Turning a Kombucha Bottle Into a Plasma Tube


Kombucha! It’s a delicious fermented beverage that is kind to your digestive system and often sold in glass bottles. You don’t just have to use those bottles for healthy drinks, though. As [Simranjit Singh] demonstrates, you can also use them to create your very own plasma tube.

[Simranjit’s] build begins with a nice large 1.4-liter kombucha bottle from the Synergy brand. To make the plasma tube nicely symmetrical, the bottle had its original spout cut off cleanly with a hot wire, with the end then sealed with a glass cap. Electrodes were installed in each end of the tube by carefully drilling out the glass and installing small bolts. They were sealed in place with epoxy laced with aluminium oxide in order to improve the dielectric strength and aid the performance of the chamber. A vacuum chamber was then used to evacuate air from inside the chamber. Once built, [Simranjit] tested the bottle with high voltage supplied from a flyback transformer, with long purple arcs flowing freely through the chamber.

A plasma tube may not be particularly useful beyond educational purposes, but it does look very cool. We do enjoy a nice high-voltage project around these parts, after all.

youtube.com/embed/eNmOGAE5OCU?…


hackaday.com/2025/03/21/turnin…


Building a Handheld Pong Game


Pong was one of the first video games to really enter the public consciousness. While it hasn’t had the staying power of franchises like Zelda or Call of Duty, it nonetheless still resonates with gamers today. That includes [Arnov Sharma], who put together this neat handheld version using modern components.

An ESP32 development board serves as the brains of the operation. Capable of operating at many hundreds of megahertz, it has an excessive amount of power for an application as simple as this. Nonetheless, it’s cheap, and it gets the job done. It’s paired with an SSD1306 OLED screen of 124 x 32 resolution. That might not sound like much, but it’s plenty when you’re just drawing two paddles and a ball bouncing between them. Control is via a pair of SMD push buttons for a nice responsive feel.

What’s really neat, though, is the presentation. [Arnov] wrapped the electronics in a neat bean-shaped housing that vaguely apes game controllers of the 16-bit era. Indeed, [Arnov] explains that it was inspired by the Sega Genesis specifically. It looks great with the black PCBs integrated so nicely with the bright orange 3D printed components, and looks quite comfortable to use, too.

It might be a simple project, but it’s done rather well. Just by thinking about color choices and how to assemble the base components, [Arnov] was able to create an attractive and functional game that’s a lot more eye catching than some random boards thrown in an old project box. Indeed, we’ve featured stories on advanced FR4/PCB construction techniques before, too. Meanwhile, if you’re creating your own projects with similar techniques, don’t hesitate to let us know!


hackaday.com/2025/03/21/buildi…


High Frequency Food: Better Cutting With Ultrasonics


You’re cutting yourself a single slice of cake. You grab a butter knife out of the drawer, hack off a moist wedge, and munch away to your mouth’s delight. The next day, you’re cutting forty slices of cake for the whole office. You grab a large chef’s knife, warm it with hot water, and cube out the sheet cake without causing too much trauma to the icing. Next week, you’re starting at your cousin’s bakery. You’re supposed to cut a few thousand slices of cake, week in, week out. You suspect your haggardly knifework won’t do.

In the home kitchen, any old knife will do the job when it comes to slicing cakes, pies, and pastries. When it comes to commercial kitchens, though, presentation is everything and perfection is the bare minimum. Thankfully, there’s a better grade of cutting tool out there—and it’s more high tech than you might think.

Shake It


Knives are very good at cutting food into distinct separate pieces. However, they have one major problem—food is sticky, and so are they. If you’ve ever cut through a cheesecake, you’ve seen this in action. Unless you’re very careful and deft with your slicing, the cake tends to grip the blade of the knife as it comes through. Try as you might, you’re almost always going to leave some marred edges unless you work very slowly.

While most home chefs and cafes can turn a blind eye to these sorts of things, that’s not the case in the processed food industry. For one thing, consumers expect each individually-packed morsel of food to be as cosmetically perfect as the last. For another, cutting processes have to be robust to work at speed. A human can compensate as they cut, freeing the blade from sticking and fettling the final product to hide their mistakes. Contrast that to a production line that slices ice cream bars from a sheet all day. All it takes is one stuck piece to completely mess up the production line and ruin the product.

youtube.com/embed/G_hPMZ2aNXQ?…

This is where ultrasonic food processing comes in. Ultrasonic cutting blades exist for one primary reason—they enable the cutting of all kinds of different foods without sticking, squashing, or otherwise marring the food. These blades most commonly find themselves used in processed food production lines, where a bulk material must be cut into individual bars or slices for later preparation or packaging.

It’s quite something to watch these blades in action. Companies like Dukane and MeiShun have demo videos that show the uncanny ability of their products to slice through even the stickiest foods without issue. You can watch cheesecakes get evenly sectored into perfect triangular slices, or a soft brie cheese being sliced without any material being left on the blade. The technique works on drier materials too—it’s possible to cut perfectly nice slices of bread with less squishing and distortion using ultrasonic blades. Even complex cakes, like the vanilla slice, with layers of stiff pastry and smooth custard, can be cut into neat polygons with appropriate ultrasonic tooling.

youtube.com/embed/0cwpbKnfO2Y?…

youtube.com/embed/xaM2N-DGCys?…

The mechanism of action is well-understood. An ultrasonic cutting blade is formally known as a sonotrode, and is still sharpened to an edge to do its job. However, where it varies from a regular blade is that it does not use mere pressure to slice through the target material. Instead, transducers in the sonotrode vibrate it at an ultrasonic frequency—beyond the range of human hearing, typically from 20 kHz to 40 kHz. When the sonotrode comes into contact with the material, the high-frequency vibrations allow it to slice through the material without sticking to it. Since the entire blade is vibrating, it continues to not stick as it slides downwards, allowing for an exceptionally clean cut.

Generally, the ultrasonic sonotrode is paired with a motion platform to move the food precisely through the cutting process, and an actuator to perform the cutting action itself. However, there are also handheld ultrasonic knives that can be purchased for those looking to use the same technique manually.

The technique isn’t solely applied to the food industry. The same techniques work for many other difficult-to-cut materials, like rubber. The technique can also be applied to various textiles or plastic materials, too. In some cases, the sonotrode can generate enough heat as it cuts through the materials to melt and seal the edges of the material it’s cutting through.

youtube.com/embed/0CesZLfD5fU?…

If you’re simply looking to cut some cake at home, this technique might be a little overly advanced for you. At the same time, there’s nothing stopping you from rigging up some transducers with a blade and a DIY CNC platform seeing what you can achieve. If you want the most perfectly cubed sheet cake at your next office party, this might just be the technology you’re looking for.


hackaday.com/2025/03/21/high-f…


Hackaday Podcast Episode 313: Capacitor Plague, Wireless Power, and Tiny Everything


We’re firmly in Europe this week on the Hackaday podcast, as Elliot Williams and Jenny List are freshly returned from Berlin and Hackaday Europe. A few days of mingling with the Hackaday community, going through mild panic over badges and SAOs, and enjoying the unique atmosphere of that city.

After discussing the weekend’s festivities we dive right into the hacks, touching on the coolest of thermal cameras, wildly inefficient but very entertaining wireless power transfer, and a restrospective on the capacitor plague from the early 2000s. Was it industrial espionage gone wrong, or something else? We also take a moment to consider spring PCB cnnectors, as used by both one of the Hackaday Europe SAOs, and a rather neat PCB resistance decade box, before looking at a tryly astounding PCB blinky that sets a new miniaturisation standard.

In our quick roundup the standouts are a 1970s British kit synthesiser and an emulated 6502 system written in shell script, and in the can’t-miss section we look at a new contender fro the smallest microcontroller, and the posibility that a century of waste coal ash may conceal a fortune in rare earth elements.

Follow the link below, to listen along!

html5-player.libsyn.com/embed/…

Want the podcast in MP3? Get it in MP3!

Where to Follow Hackaday Podcast

Places to follow Hackaday podcasts:



Episode 312 Show Notes:

What’s that Sound?



Interesting Hacks of the Week:



Quick Hacks:



Can’t-Miss Articles:



hackaday.com/2025/03/21/hackad…


Benchtop Haber-Bosch Makes Ammonia at Home


Humans weren’t the first organisms on this planet to figure out how to turn the abundance of nitrogen in the atmosphere into a chemically useful form; that honor goes to some microbes that learned how to make the most of the primordial soup they called home. But to our credit, once [Messrs. Haber and Bosch] figured out how to make ammonia from thin air, we really went gangbusters on it, to the tune of 8 million tons per year of the stuff.

While it’s not likely that [benchtop take on the Haber-Bosch process demonstrated by [Marb’s lab] will turn out more than the barest fraction of that, it’s still pretty cool to see the ammonia-making process executed in such an up close and personal way. The industrial version of Haber-Bosch uses heat, pressure, and catalysts to overcome the objections of diatomic nitrogen to splitting apart and forming NH3; [Marb]’s version does much the same, albeit at tamer pressures.

[Marb]’s process starts with hydrogen made by dripping sulfuric acid onto zinc strips and drying it through a bed of silica gel. The dried hydrogen then makes its way into a quartz glass reaction tube, which is heated by a modified camp stove. Directly above the flame is a ceramic boat filled with catalyst, which is a mixture of aluminum oxide and iron powder; does that sound like the recipe for thermite to anyone else?

A vial of Berthelot’s reagent, which [Marb] used in his recent blood ammonia assay, indicates when ammonia is produced. To start a run, [Marb] first purges the apparatus with nitrogen, to prevent any hydrogen-related catastrophes. After starting the hydrogen generator and flaring off the excess, he heats up the catalyst bed and starts pushing pure nitrogen through the chamber. In short order the Berthelot reagent starts turning dark blue, indicating the production of ammonia.

It’s a great demonstration of the process, but what we like about it is the fantastic tips about building lab apparatus on the cheap. Particularly the idea of using hardware store pipe clamps to secure glassware; the mold-it-yourself silicone stoppers were cool too.

youtube.com/embed/31jpvFuUQBI?…


hackaday.com/2025/03/21/bencht…


This Week in Security: The Github Supply Chain Attack, Ransomware Decryption, and Paragon


Last Friday Github saw a supply chain attack hidden in a popular Github Action. To understand this, we have to quickly cover Continuous Integration (CI) and Github Actions. CI essentially means automatic builds of a project. Time to make a release? CI run. A commit was pushed? CI run. For some projects, even pull requests trigger a CI run. It’s particularly handy when the project has a test suite that can be run inside the CI process.

Doing automated builds may sound straightforward, but the process includes checking out code, installing build dependencies, doing a build, determining if the build succeeded, and then uploading the results somewhere useful. Sometimes this even includes making commits to the repo itself, to increment a version number for instance. For each step there are different approaches and interesting quirks for every project. Github handles this by maintaining a marketplace of “actions”, many of which are community maintained. Those are reusable code snippets that handle many CI processes with just a few options.

One other element to understand is “secrets”. If a project release process ends with uploading to an AWS store, the process needs an access key. Github stores those secrets securely, and makes them available in Github Actions. Between the ability to make changes to the project itself, and the potential for leaking secrets, it suddenly becomes clear why it’s very important not to let untrusted code run inside the context of a Github Action.

And this brings us to what happened last Friday. One of those community maintained actions, tj-actions/changed-files, was modified to pull an obfuscated Python script and run it. That code dumps the memory of the Github runner process, looks for anything there tagged with isSecret, and writes those values out to the log. The log, that coincidentally, is world readable for public repositories, so printing secrets to the log exposes them for anyone that knows where to look.

Researchers at StepSecurity have been covering this, and have a simple search string to use: org:changeme tj-actions/changed-files Action. That just looks for any mention of the compromised action. It’s unclear whether the compromised action was embedded in any other popular actions. The recommendation is to search recent Github Action logs for any mention of changed-files, and start rotating secrets if present.

Linux Supply Chain Research


The folks at Fenrisk were also thinking about supply chain attacks recently, but specifically in how Linux distributions are packaged. They did find a quartet of issues in Fedora’s Pagure web application, which is used for source code management for Fedora packages. The most severe of them is an argument injection in the logging function, allowing for arbitrary file write.

The identifier option is intended to set the branchname for a request, but it can be hijacked in a request, injecting the output flag: [url=http://pagure.local/test/history/README.md?identifier=--output=/tmp/foo.bar]http://pagure.local/test/history/README.md?identifier=--output=/tmp/foo.bar[/url]. That bit of redirection will output the Git history to the file specified. Git history consists of a git hash, and then the short commit message. That commit message has very little in the way of character scrubbing, so Bash booleans like || can be used to smuggle a command in. Add the cooked commit to your local branch of something, query the URL to write the file history to your .bashrc file, and then attempt to SSH in to the Pagure service. The server does the right thing with the SSH connection, refusing to give the user a shell, but not before executing the code dropped into the .bashrc file. This one was disclosed in April 2024, and was fixed within hours of disclosure by Red Hat.

Pagure was not the only target, and Fenrisk researchers also discovered a critical vulnerability in OpenSUSE’s Open Build Service. It’s actually similar to the Fedora Pagure issue. Command options can be injected into the wget command used to download the package source file. The --output-document argument can be used to write arbitrary data to a file in the user’s home directory, but there isn’t an obvious path to executing that file. There are likely several ways this could be accomplished, but the one chosen for this Proof of Concept (PoC) was writing a .proverc file in the home directory. Then a second wget argument is injected, using --use-askpass to trigger the prove binary. It loads from the local rc file, and we have arbitrary shell code execution. The OpenSUSE team had fixes available and rolled out within a few days of the private disclosure back in June of 2024.

Breaking Ransomware Encryption


What do you do when company data is hit with Akira ransomware, and the backups were found wanting? If you’re [Yohanes Nugroho], apparently you roll up your sleeves and get to work. This particular strain of Akira has a weakness that made decryption and recovery seemingly easy. The encryption key was seeded by the current system time, and [Yohanes] had both system logs and file modification timestamps to work with. That’s the danger of using timestamps for random seeds. If you know the timestamp, the pseudorandom sequence can be derived.

It turns out, it wasn’t quite that easy. This strain of Akira actually used four separate nanosecond scale time values in determining the per-file encryption key. Values we’ll call t3 and t4 are used to seed the encryption used for the first eight bytes of each file. If there’s any hope of decrypting these files, those two values will have to be found first. Through decompiling the malware binaries, [Yohanes] knew that the malware process would start execution, then run a fixed amount of code to generate the t3 key, and a fixed amount of code before generating the t4 key. In an ideal world, that fixed code would take a fixed amount of time to run, but multi-core machines, running multi-threaded operations on real hardware will introduce variations in that timing.

The real-world result is a range of possible time offsets for both those values. Each timestamp from the log results in about 4.5 quadrillion timestamp pairs. Because the timing is more known, once t3 and t4 are discovered, finding t1 and t2 is much quicker. There are some fun optimizations that can be done, like generating a timestamp to pseudorandom value lookup table. It works well ported to CUDA, running on an RTX 4090. In the end, brute-forcing a 10 second slice of timestamps cost about $1300 dollars when renting GPUs through a service like vast.ai. The source code that made this possible isn’t pretty, but [Yohanes] has made it all available if you want to attempt the same trick.

Github and Ruby-SAML — The Rest of the Story


Last week we briefly talked about Github’s discovery of the multiple parser problem in Ruby-SAML, leading to authentication bypass. Researchers at Portswigger were also working on this vulnerability, and have their report out with more details. One of those details is that while Github had already moved away from using this library, Gitlab Enterprise had not. This was a real vulnerability on Gitlab installs, and if your install is old enough, maybe it still is.

The key here is a CDATA section wrapped in an XML comment section is only seen by one of the parsers. Include two separate assertion blocks, and you get to drive right through the difference between the two parsers.

Paragon


There’s a new player in the realm of legal malware. Paragon has reportedly targeted about 90 WhatsApp users with a zero-click exploit, using a malicious PDF attachment to compromise Android devices. WhatsApp has mitigated this particular vulnerability on the server side.

It’s interesting that apparently there’s something about the process of adding the target user to the WhatsApp group that was important to making the attack work. Paragon shares some similarities with NSO Group, but maintains that it’s being more careful about who those services are being offered to.

Bits and Bytes


We have a pair of local privilege escalation attacks. This is useful when an attacker has unprivileged access to a machine, but can use already installed software to get further access. The first is Google’s Web Designer, that starts a debug port, and exposes an account token and file read/right to the local system. The other is missing quotation marks in Plantronics Hub, which leads to the application attempting to execute C:\Program.exe before it descends into Program Files to look for the proper location.

This is your reminder, from Domain Guard, to clean up your DNS records. I’ve now gone through multiple IP address changes of my “static” IP Addresses. At the current rate of IPv4 exhaustion, those IPs are essentially guaranteed to be given out to somebody else. Is it a problem to have dangling DNS records? It’s definitely not a good situation, because it enables hacks from cross-site scripting vulnerabilities, to cookie stealing, to potentially defeating domain verification schemes with the errant subdomain.

MacOS has quite a fine history of null-pointer dereference vulnerabilities. That’s when a pointer is still set to NULL, or 0, and the program errantly tries to access that memory location. It used to be that a clever attacker could actually claim memory location 0, and take advantage of the bogus dereference. But MacOS put an end to that technique in a couple different ways, the most effective being disallowing 32 bit processes altogether in recent releases. It seems that arbitrary code execution on MacOS as result of a NULL Pointer Dereference is a thing of the past. And yes, we’re quite aware that this statement means that somehow, someone will figure out a way to make it happen.

And Finally, watchTowr is back with their delightful blend of humor and security research. This time it’s a chain of vulnerabilities leading to an RCE in Kentico, a proprietary web Content Management System. This vulnerability has one of my least favorite data formats, SOAP XML. It turns out Kentico’s user authentication returns an empty string instead of a password hash when dealing with an invalid username. And that means you can craft a SOAP authenticaiton token with nothing more than a valid nonce and timestamp. Whoops. The issue was fixed in a mere six days, so good on Kentico for that.


hackaday.com/2025/03/21/this-w…


Aluminum Business Cards Make Viable PCB Stencils


[Mikey Sklar] had a problem—namely, running low on the brass material typically used for making PCB stencils. Thankfully, a replacement material was not hard to find. It turns out you can use aluminum business card blanks to make viable PCB stencils.

Why business card blanks? They’re cheap, for a start—maybe 15 cents each in quantity. They’re also the right thickness, at just 0.8 mm, and they’re flat, unlike rolled materials that can tend to flip up when you’re trying to spread paste. They’re only good for small PCBs, of course, but for many applications, they’ll do just fine.

To cut these, you’ll probably want a laser cutter. [Mikey] was duly equipped in that regard already, which helped. Using a 20 watt fiber laser at a power of 80%, he was able to get nice accurate cuts for the stencils. Thanks to the small size of the PCBs in question, the stencils for three PCBs could be crammed on to a single card.

If you’re not happy with your existing PCB stencil material, you might like to try these aluminium blanks on for size. We’ve covered other stenciling topics before, too.

youtube.com/embed/vPO3uMIyp_U?…


hackaday.com/2025/03/21/alumin…


Threat landscape for industrial automation systems in Q4 2024



Statistics across all threats


In Q4 2024, the percentage of ICS computers on which malicious objects were blocked decreased by 0.1 pp from the previous quarter to 21.9%.

Percentage of ICS computers on which malicious objects were blocked, by quarter, 2022–2024
Percentage of ICS computers on which malicious objects were blocked, by quarter, 2022–2024

Compared to Q4 2023, the percentage decreased by 2.8 pp.

The percentage of ICS computers on which malicious objects were blocked during Q4 2024 was highest in October and lowest in November. In fact, the percentage in November 2024 was the lowest of any month in two years.

Percentage of ICS computers on which malicious objects were blocked, Jan 2023–Dec 2024
Percentage of ICS computers on which malicious objects were blocked, Jan 2023–Dec 2024

Region rankings


Regionally, the percentage of ICS computers that blocked malicious objects during the quarter ranged from 10.6% in Northern Europe to 31% in Africa.

Regions ranked by percentage of ICS computers where malicious objects were blocked, Q3 2024
Regions ranked by percentage of ICS computers where malicious objects were blocked, Q3 2024

Eight of 13 regions saw their percentages increase from the previous quarter.

Regions and world. Changes in the percentage of attacked ICS computers in Q4 2024
Regions and world. Changes in the percentage of attacked ICS computers in Q4 2024

Selected industries


The biometrics sector led the surveyed industries in terms of the percentage of ICS computers on which malicious objects were blocked.

Percentage of ICS computers on which malicious objects were blocked in selected industries
Percentage of ICS computers on which malicious objects were blocked in selected industries

In Q4 2024, the percentage of ICS computers on which malicious objects were blocked decreased across most industries, with the exception of the construction sector.

Changes in the percentage of ICS computers on which malicious objects were blocked in selected industries
Changes in the percentage of ICS computers on which malicious objects were blocked in selected industries

Diversity of detected malicious objects


In Q4 2024, Kaspersky’s protection solutions blocked malware from 11,065 different malware families of various categories on industrial automation systems.

Percentage of ICS computers on which the activity of malicious objects from various categories was blocked
Percentage of ICS computers on which the activity of malicious objects from various categories was blocked

Main threat sources


The internet, email clients and removable storage devices remain the primary sources of threats to computers in an organization’s technology infrastructure. Note that the sources of blocked threats cannot be reliably identified in all cases.

In Q4 2024, the percentage of ICS computers on which threats from various sources were blocked decreased for all threat sources described in this report. Moreover, all indicators recorded their lowest values for the observed period.

Percentage of ICS computers on which malicious objects from various sources were blocked
Percentage of ICS computers on which malicious objects from various sources were blocked

Threat categories

Malicious objects used for initial infection


Malicious objects used for initial infection of ICS computers include dangerous internet resources that are added to denylists, malicious scripts and phishing pages, and malicious documents.

In the fourth quarter of 2024, the percentage of ICS computers on which malicious documents and denylisted internet resources were blocked decreased to 1.71% (by 0.26 pp) and 5.52% (by 1.32 pp), respectively and reached its lowest level since the beginning of 2022.

As noted in the Q3 2024 report, the increase in blocked denylisted internet resources was primarily driven by an increase in the number of newly created domain names and IP addresses used by cybercriminals as command-and-control (C2) infrastructure for distributing malware and phishing attacks.

The decline in the percentage of denylisted internet resources in November–December 2024 was likely influenced not only by proactive threat mitigation measures at various levels – from resource owners and hosting providers to ISPs and law enforcement agencies. Another contributing factor was the tendency of attackers to frequently change domains and IP addresses to evade detection in the initial stages, based on lists of known malicious resources.

In practice, this means that until a malicious web resource is identified and added to a denylist, it may not immediately appear in threat statistics, leading to an apparent decrease in the percentage of ICS computers on which such resources were blocked.

However, in Q4, we also saw a rise in the percentage of the next steps in the attack chain – malicious scripts and phishing pages (7.11%), spyware (4.30%), and ransomware (0.21%).

A significant increase in the percentage of malicious scripts and phishing pages in October was driven by a series of widespread phishing attacks in late summer and early fall 2024, as mentioned in the Q3 2024 report. Threat actors used malicious scripts that executed in the browser, mimicking various windows with CAPTCHA-like interfaces, browser error messages and similar pop-ups to trigger the download of next-stage malware: either the Lumma stealer or the Amadey Trojan.

Next-stage malware


Malicious objects used to initially infect computers deliver next-stage malware – spyware, ransomware, and miners – to victims’ computers. As a rule, the higher the percentage of ICS computers on which the initial infection malware is blocked, the higher the percentage for next-stage malware.

The percentage of ICS computers on which spyware (spy Trojans, backdoors and keyloggers) was blocked increased by 0.39 pp from the previous quarter to 4.30%.

The percentage of ICS computers on which ransomware was blocked increased by a factor of 1.3 compared to the previous quarter, reaching 0.21%, its highest value in two years.

The percentage of ICS computers on which miners in the form of executable files for Windows were blocked decreased by 0.01 pp to 0.70%.

And, the percentage of ICS computers on which web miners were blocked decreased by 0.02 pp to 0.39%, reaching its lowest value in the observed period.

Self-propagating malware


Self-propagating malware (worms and viruses) is a category unto itself. Worms and virus-infected files were originally used for initial infection, but as botnet functionality evolved, they took on next-stage characteristics. To spread across ICS networks, viruses and worms rely on removable media, network folders, infected files including backups, and network attacks on outdated software.

In Q4 2024, the percentage of ICS computers on which worms were blocked increased by 0.07 pp and reached 1,37%. The rate of viruses increased by 0.08 pp to 1.61%.

AutoCAD malware


AutoCAD malware is typically a low-level threat, coming last in the malware category rankings in terms of the percentage of ICS computers on which it was blocked.

In Q4 2024, the percentage of ICS computers on which AutoCAD malware was blocked continued to decrease by losing 0.02 pp and reached 0.38%.

You can find the full Q3 2024 report on the Kaspersky ICS CERT website.


securelist.com/ics-cert-q4-202…


Cheap Endoscopic Camera Helps Automate Pressure Advance Calibration


The difference between 3D printing and good 3D printing comes down to attention to detail. There are so many settings and so many variables, each of which seems to impact the other to a degree that can make setting things up a maddening process. That makes anything that simplifies the process, such as this computer vision pressure advance attachment, a welcome addition to the printing toolchain.

If you haven’t run into the term “pressure advance” for FDM printing before, fear not; it’s pretty intuitive. It’s just a way to compensate for the elasticity of the molten plastic column in the extruder, which can cause variations in the amount of material deposited when the print head acceleration changes, such as at corners or when starting a new layer.

To automate his pressure advance calibration process, [Marius Wachtler] attached one of those dirt-cheap endoscope cameras to the print head of his modified Ender 3, pointing straight down and square with the bed. A test grid is printed in a corner of the bed, with each arm printed using a slightly different pressure advance setting. The camera takes a photo of the pattern, which is processed by computer vision to remove the background and measure the thickness of each line. The line with the least variation wins, and the pressure advance setting used to print that line is used for the rest of the print — no blubs, no blebs.

We’ve seen other pressure-advanced calibrators before, but we like this one because it seems so cheap and easy to put together. True, it does mean sending images off to the cloud for analysis, but that seems a small price to pay for the convenience. And [Marius] is hopeful that he’ll be able to run the model locally at some point; we’re looking forward to that.

youtube.com/embed/LptiyxAR9nc?…


hackaday.com/2025/03/21/cheap-…


Cucù, Lo 0day di Graphite non c’è più! Whatsapp risolve il bug usato per colpire gli italiani


Ne avevamo discusso di recente, analizzando il caso Paragon in Italia, che ha portato alla sorveglianza di diversi cittadini italiani. Uno scandalo che, come spesso accade, ha sollevato polemiche per poi finire rapidamente nel dimenticatoio.

WhatsApp ha corretto una vulnerabilità zero-day sfruttata per installare lo spyware Graphite di Paragon. Lo Sviluppatore di spyware israeliano Paragon Solutions Ltd. è stata fondata nel 2019. Secondo quanto riportato dai media, nel dicembre 2024 la società è stata acquisita dal gruppo di investimento AE Industrial Partners con sede in Florida.

A differenza dei suoi concorrenti (come NSO Group), Paragon afferma di vendere i suoi strumenti di sorveglianza solo alle forze dell’ordine e alle agenzie di intelligence dei paesi democratici che hanno bisogno di rintracciare criminali pericolosi. Il 31 gennaio 2025, dopo aver risolto la vulnerabilità zero-click, i rappresentanti di WhatsApp hanno notificato a circa 90 utenti Android di 20 Paesi (tra cui giornalisti e attivisti italiani) di essere stati vittime di attacchi da parte dello spyware Paragon, progettato per raccogliere dati sensibili e intercettare i loro messaggi privati.

Come hanno ora rivelato gli esperti di Citizen Lab , gli aggressori hanno aggiunto le future vittime ai gruppi WhatsApp e poi hanno inviato loro un file PDF. Il dispositivo della vittima ha elaborato il file dando accesso all’exploit 0-day che ha consentito l’installazione dello spyware Graphite.

Successivamente il malware è fuoriuscito dalla sandbox di Android e ha compromesso altre app sui dispositivi delle vittime. Inoltre, dopo l’installazione, lo spyware forniva ai suoi operatori l’accesso ai messaggi di messaggistica degli utenti. A quanto si dice, lo spyware può essere rilevato sui dispositivi Android con jailbreak tramite un artefatto denominato BIGPRETZEL. È possibile scoprirlo analizzando i registri dei dispositivi hackerati.

Gli esperti di Citizen Lab hanno mappato l’infrastruttura server utilizzata da Paragon per installare Graphite sui dispositivi delle vittime e hanno trovato possibili collegamenti tra l’azienda e diversi clienti governativi, tra cui Australia, Canada, Cipro, Danimarca, Israele e Singapore. In totale, sono stati in grado di identificare 150 certificati digitali associati a decine di indirizzi IP che, secondo i ricercatori, fanno parte dell’infrastruttura di controllo di Paragon.

“L’infrastruttura includeva server cloud che erano probabilmente stati affittati da Paragon o dai suoi clienti, così come server che potrebbero essere stati ubicati nei locali di Paragon e dei suoi clienti governativi. L’infrastruttura scoperta era collegata a pagine web chiamate “Paragon” che venivano restituite da indirizzi IP in Israele (dove ha sede Paragon), nonché a un certificato TLS contenente il nome dell’organizzazione Graphite. Lo stesso nome è dato allo spyware Paragon. È stato trovato anche un nome comune “installerserver”. Il prodotto spyware concorrente Pegasus usa il termine “Installation Server” per riferirsi ai server progettati per infettare i dispositivi con spyware”, scrivono gli esperti.

Secondo i rappresentanti di WhatsApp, questo vettore di attacco è stato risolto alla fine del 2024 e non ha richiesto patch lato client. L’azienda ha affermato di aver deciso di non assegnare un identificatore CVE alla vulnerabilità dopo “aver esaminato le linee guida CVE pubblicate da MITRE e a causa delle politiche interne dell’azienda”.

L'articolo Cucù, Lo 0day di Graphite non c’è più! Whatsapp risolve il bug usato per colpire gli italiani proviene da il blog della sicurezza informatica.


Il Dossier Segreto su BlackBasta : Cosa imparare dei retroscena inediti di una Ransomware Gang


Nel libro “l’arte della Guerra” Sun Tzu scrisse “Se conosci il nemico e te stesso, la tua vittoria è sicura“.

Conoscere il nemico è un aspetto fondamentale di qualunque campo di battaglia, compreso quello della sicurezza informatica. Per questo motivo il lavoro di DarkLab, appena pubblicato per Red Hot Cyber, ha una rilevanza senza pari.

Cosa è accaduto: qualche tempo si è realizzato un data leak che ha visto la pubblicazione di moltissime chat e comunicazioni intercorse tra gli affiliati ad una temutissima gang di criminali informatici, specializzata in ransomware. DarkLab ha analizzato questi documenti e ne ha ricavato un dossier (di facile e veloce lettura, che consiglio vivamente).

Questo report è importantissimo poiché ci consente di vedere cosa e come funziona “dall’altra parte”, traendone informazioni utili che qualunque ente e azienda potrebbero convertire in misure di sicurezza. Qui mi interessa evidenziarne alcune, per il resto (struttura, tattiche di negoziazione dei riscatti, ecc…) vi consiglio vivamente di leggere il rapporto che trovate qui

Le VPN sono bersagli particolarmente attenzionati dai criminali informatici, i quali destinano investimenti mirati per lo sfruttamento delle loro vulnerabilità.

Insegnamento: prestare particolare attenzione e investire particolarmente sulla protezione delle VPN

Tecniche di social Engineering avanzate: la gang ha un operatore dedicato, specializzato nel contatto di personale chiave nelle aziende vittime. Una delle tecniche sviluppate è quella di impersonificare un operatore del dipartimento IT per ottenere accesso ai sistemi delle vittime, anche attraverso call center per rendere tutto più credibile.

Insegnamento: redigere delle politiche ad hoc per i contatti dell’ufficio IT con il personale aziendale, e fare in modo che ne siano tutti informati, in modo tale da non dare seguito a richieste effettuate in maniera non proceduralizzata.

per evitare la detection agiscono con molta calma, fino ad arrivare a lanciare solo un comando al giorno. Inoltre, hanno fatto ricorso ad una mail fingendosi il supporto tecnico interno al fine di mascherare talune operazioni.

Insegnamento: ancora una volta emerge come l’impersonificazione del reparto IT sia un vettore chiave per molti attacchi. Proceduralizzare delle modalità di contatto dei servizi IT, da mantenere riservate, costituisce una importante contromisura.

I criminali informatici cercano di evitare attacchi a realtà che implementano la MFA.

Insegnamento: MFA è uno strumento che può essere un forte disincentivo all’attacco criminale.

Una tecnica molto utilizzata era il phishing mediante Microsoft Teams con un “pretext” standard.

Insegnamento: sviluppare politiche interne per qualunque tipo di comunicazione. Queste politiche sono da mantenere riservate e conosciute solo al personale a cui è fatto divieto di diffonderle. Insegnare a riconoscere i messaggi di phishing all’interno dell’azienda elimina uno strumento di attacco ai criminali.

Tutte queste informazioni sono preziosissime per chi si deve difendere, poiché consente di conoscere le metodologie di attacco e di adottare le contromisure più opportune e adeguate.

Conoscere il proprio nemico è fondamentale, ma altrettanto importante è conoscere se stessi, e forse è da questo punto che molte realtà dovrebbero iniziare poiché troppo spesso c’è poca consapevolezza.

L'articolo Il Dossier Segreto su BlackBasta : Cosa imparare dei retroscena inediti di una Ransomware Gang proviene da il blog della sicurezza informatica.


A Modern Take on the Etch A Sketch


The Etch A Sketch is a classic children’s toy resembling a picture frame where artwork can be made by turning two knobs attached to a stylus inside the frame. The stylus scrapes off an aluminum powder, creating the image which can then be erased by turning the frame upside down and shaking it, adding the powder back to the display. It’s completely offline and requires no batteries, but in our modern world those two things seem to be more requirements than when the Etch A Sketch was first produced in the 1960s. Enter the Tilt-A-Sketch, a modern version of the classic toy.

Rather than use aluminum powder for the display, the Tilt A Sketch replaces it with an LED matrix and removes the stylus completely. There are no knobs on this device to control the path of the LED either; a inertial measurement unit is able to sense the direction that the toy is tilted while a microcontroller uses that input to light up a series of LEDs corresponding to the direction of tilt. There are a few buttons on the side of the device as well which allow the colors displayed by the LEDs to change, and similar to the original toy the display can be reset by shaking.

The Tilt-A-Sketch was built by [devitoal] as part of an art display which allows the visitors to create their own art. Housed in a laser-cut wooden enclosure the toy does a faithful job of recreating the original. Perhaps unsurprisingly, the Etch A Sketch is a popular platform for various projects that we’ve seen before including original toys modified with robotics to create the artwork and electronic recreations that use LED displays instead in a way similar to this project.

youtube.com/embed/KoSKXEI5jus?…


hackaday.com/2025/03/20/a-mode…


Solar Power, Logically


We’ve all seen the ads. Some offer “free” solar panels. Others promise nearly free energy if you just purchase a solar — well, solar system doesn’t sound right — maybe… solar energy setup. Many of these plans are dubious at best. You pay for someone to mount solar panels on your house and then pay them for the electricity they generate at — presumably — a lower cost than your usual source of electricity. But what about just doing your own set up? Is it worth it? We can’t answer that, but [Brian Potter] can help you answer it for yourself.

In a recent post, he talks about the rise of solar power and how it is becoming a large part of the power generation landscape. Interestingly, he presents graphs of things like the cost per watt of solar panels adjusted for 2023 dollars. In 1975, a watt cost over $100. These days it is about $0.30. So the price isn’t what slows solar adoption.

The biggest problem is the intermittent nature of solar. But how bad is that really? It depends. If you can sell power back to the grid when you have it to spare and then buy it back later, that might make sense. But it is more effective to store what you make for your own use.

That, however, complicates things. If you really want to go off the grid, you need enough capacity to address your peak demand and enough storage to meet demand over several days to account for overcast days, for example.

There’s more to it than just that. Read the post for more details. But even if you don’t want solar, if you enjoy seeing data-driven analysis, there is plenty to like here.

Building an effective solar power system is within reach of nearly anyone these days. Some of the problems with solar go away when you put the cells in orbit. Of course, that always raises new problems.


hackaday.com/2025/03/20/solar-…