Cybersecurity & cyberwarfare ha ricondiviso questo.

The media in this post is not displayed to visitors. To view it, please go to the original post.

1-Click GitHub Token Theft: VSCode Webview Flaw Exposes OAuth Tokens for All Private Repositories
#CyberSecurity
securebulletin.com/1-click-git…
Cybersecurity & cyberwarfare ha ricondiviso questo.

The media in this post is not displayed to visitors. To view it, please go to the original post.

CISA Adds Oracle WebLogic CVE-2024-21182 to KEV Catalog as Active Exploitation Confirmed — Patch by June 4
#CyberSecurity
securebulletin.com/cisa-adds-o…
Cybersecurity & cyberwarfare ha ricondiviso questo.

The media in this post is not displayed to visitors. To view it, please go to the original post.

Documentazione tecnica: un obbligo sottovalutato ma un pilastro della sicurezza

📌 Link all'articolo : redhotcyber.com/post/documenta…

A cura di Stefano Toffano

#redhotcyber #news #gestioneinfrastrutture #manutenzione #rete #pmi #informatica #tecnologia

Cybersecurity & cyberwarfare ha ricondiviso questo.

📺 Risky Business Weekly (840): Microsoft walks back researcher threats

risky.biz/video/risky-business…

reshared this

Cybersecurity & cyberwarfare ha ricondiviso questo.

The media in this post is not displayed to visitors. To view it, please go to the original post.

329 – La ragione per cui si bannano i prodotti cinesi camisanicalzolari.it/329-la-ra…

reshared this

Cybersecurity & cyberwarfare ha ricondiviso questo.

The media in this post is not displayed to visitors. To view it, please go to the original post.

💥🚨 FLASH SALE: -10% FINO AL 7 GIUGNO PER L'OTTAVA LIVE CLASS "DARKWEB & CYBER THREAT INTELLIGENCE" IN PARTENZA A LUGLIO

QUATTRO LEZIONI PER COMPRENDERE IL DARKWEB ED ENTRARE DA PROTAGONISTI NELLA CYBER THREAT INTELLIGENCE.
Per info e iscrizioni: 📱 💬 379 163 8765 ✉️ formazione@redhotcyber.com

✅ Pagina del corso: redhotcyber.com/linksSk2L/acad…
✅ Presentazione del corso del prof. Pietro Melillo : youtube.com/watch?v=9VaQUnTz4J…
✅ Webinar introduttivo di presentazione al corso : youtube.com/watch?v=ExZhKqjuwf…
✅ Workshop di DarkLab alla RHC Conference 2026 : youtube.com/watch?v=yE1Li3TS5B…

#redhotcyber #formazione #formazioneonline #ethicalhacking #cti #cyberthreatintelligence #cybersecurity #cybercrime #cybersecuritytraining #cybersecuritynews #privacy #cti #cyberthreat #intelligence #infosec #corsi #corsiprartici #liveclass

Cybersecurity & cyberwarfare ha ricondiviso questo.

The media in this post is not displayed to visitors. To view it, please go to the original post.

Relazione annuale ACN 2025 : aumento degli attacchi, ma difese più efficaci

📌 Link all'articolo : redhotcyber.com/post/relazione…

A cura di Paolo Galdieri

#redhotcyber #news #cybersecurity #hacking #malware #ransomware #sicurezzainformatica

Cybersecurity & cyberwarfare ha ricondiviso questo.

The media in this post is not displayed to visitors. To view it, please go to the original post.

Workshop RHC Conference 2026 - Block Me If You Can: Difendere gli LLM dal Prompt Injection

Guarda il video: youtube.com/watch?v=XeZF6kuohH…

#redhotcyber #rhcconference #conferenza #informationsecurity #ethicalhacking #dataprotection

Cybersecurity & cyberwarfare ha ricondiviso questo.

The media in this post is not displayed to visitors. To view it, please go to the original post.

Il Grande Fratello entra in ufficio: il Garante ferma l’IA che valuta lo stress dei dipendenti

📌 Link all'articolo : redhotcyber.com/post/il-grande…

A cura di Carolina Vivianti

#redhotcyber #news #protezionedatidipersonali #privacylavoro #intelligenzaartificiale

Turning an Old 3D Printer Into a Vinyl Cutter for Cheap


The media in this post is not displayed to visitors. To view it, please log in.

Replacing a 3D printer’s extruder with a cutting blade seems like an easy way to do things like vinyl cutting, but you cannot just put on any blade and expect good results. The right type of blade is called a drag knife and it’s designed so that it follows the direction in which you’re cutting. You can get these in dedicated vinyl cutting machines, as well as in the form of attachments for the likes of CNC machines. How to use them with an old Anycubic Mega S FDM printer is demonstrated by [Cocoanix 3D Printing] in a recent video.

For a bit more background information you can peruse for example this write-up by [Kronos Robotics], who goes through the steps of selecting the right blade, cutting mat and such for use with a CNC machine.

For the 3D printer in the video a Roland vinyl cutter style holder and blades were bought off AliExpress, for which then a custom 3D printed mount was designed, though you can often get a ready-made one off your usual 3D model sources. Following this you get into the hardest part, being the software and making sure you don’t cut too deep into the vinyl through its backing paper.

Fortunately most of the hard work here is done already by the Polycut project, which is precisely designed to help you turn a 3D printer or similar into a vinyl cutter or plotter. This takes in an SVG file and generates the appropriate g-code, after which you better have gotten your Z-offset calibration right if you want that perfect result. With all that in place it’s then actually quite easy to cut your very own vinyl without shelling out big bucks for a dedicated machine.

Of course, it’ll likely never be as fast as those machines, requires more calibration and have a more limited cutting space, but as it’s not a permanent modification and probably less crazy than putting a laser engraver module on a commercial FDM printer like the Bambu Lab H2D.

youtube.com/embed/KcpcjyyMpYQ?…


hackaday.com/2026/06/02/turnin…

Cybersecurity & cyberwarfare ha ricondiviso questo.

Why an #HP Poly #VoIP Phones Bug Could Become an Enterprise Foothold
securityaffairs.com/193045/sec…
#securityaffairs #hacking
Cybersecurity & cyberwarfare ha ricondiviso questo.

The media in this post is not displayed to visitors. To view it, please go to the original post.

La connessione internet in Iran: Perché la sua interruzione è un problema serio

📌 Link all'articolo : redhotcyber.com/post/la-connes…

A cura di Silvia Felici

#redhotcyber #news #iran #internet #cloudcomputing #ecommerce #istruzioneonline #censura

Cybersecurity & cyberwarfare ha ricondiviso questo.

The media in this post is not displayed to visitors. To view it, please go to the original post.

327 – Cosa fanno i nostri figli con l’AI mentre noi dormiamo camisanicalzolari.it/327-cosa-…

A High-Vacuum Controller for an Eventual Electron Microscope


The media in this post is not displayed to visitors. To view it, please log in.

A black plastic box is shown, with a green circuit board inside. The circuit board is wired to an RS-232 connector and an RJ-45 connector.

[Chris Doble] has high ambitions: he’s making his own scanning-electron microscope, and as the first step he’s built a high-vacuum system. This required its own controller to manage the various electronics involved in the system, which he’s documented and open-sourced.

The vacuum system itself starts with a rotary-vane roughing pump, which can bring a chamber down from atmospheric pressure to about 10-3 millibar. This is still too high a pressure, so the second stage is a turbomolecular high-vacuum pump, which can operate from 18 millibar down to 10-7 millibar. To protect the turbomolecular pump in case the roughing pump suddenly stops, it includes an anti-suckback valve. Connected to these pumps is a pressure gauge which uses a pair of sensors to sense the entire pressure range. All this setup worked well, but the turbomolecular pump and the pressure sensor each used their own interfaces, while [Chris] wanted a single interface for the eventual microscope.

[Chris] therefore designed his own controller based on the Raspberry Pi Pico 2, with firmware written in Rust. The pressure gauge uses an RS-232 interface, which he connected to the Pico’s UART pins using an RS-232 level shifter, with a null modem to swap over the transmitting and receiving pins. The turbomolecular pump used an RS-485 interface, which required a converter circuit and some level-shifting resistors. A custom PCB and 3D-printed case hold the final circuit, which provides a host computer with a single USB interface. When [Chris] tested the controller, the vacuum chamber reached a pressure of 10-6 millibar, and was still slowly falling when he ended the test.

This isn’t the first vacuum chamber controller we’ve seen. Of course, this assumes that the pressure gauge already has a controller; if not, we’ve also covered one of those. To see the inspiration for [Chris]’s project, check out [Ben Krasnow]’s scanning-electron microscope.

youtube.com/embed/Ku04_mVZx_E?…


hackaday.com/2026/06/02/a-high…

Cybersecurity & cyberwarfare ha ricondiviso questo.

The media in this post is not displayed to visitors. To view it, please go to the original post.

Folks, please for the love of god, stop sending Operation Zero your AI slop bug reports.

Y’all know that what they really like are government-grade stolen 0days.

Cybersecurity & cyberwarfare ha ricondiviso questo.

The media in this post is not displayed to visitors. To view it, please go to the original post.

Folks, please for the love of god, stop sending Operation Zero your AI slop bug reports.

Y’all know that what they really like are government-grade stolen 0days.

Does Your Terminal Speak Morse? This One Does


The media in this post is not displayed to visitors. To view it, please log in.

There are a lot of single board computers on the market these days, so you can be forgiven if you missed the LuckFox Lyra. Its main claim to fame seems to be that it shares the Pi Pico’s 51 mm x 21 mm footprint while being powerful enough to run a full Linux system– or at least, it was. Now its claim to fame is as a device you can interact with no peripherals, accessing the terminal via Morse code. That’s thanks to [Gabriel Broussard Korr] and his Morstdin project, which should run on just about anything POSIX-compliant, by dint of a being a clever sh script at heart.

Of course, with most POSIX-compliant systems, you’ll need to alter the script to account for some kind of periferal to do the Morse I/O– not so on the LuckFox Lyra, which has a built-in LED and a single usable button. It actually has two buttons, but one of them is RESET and you can’t use that for anything but its intended purpose. The BOOT button, on the other hand, becomes user input after the system has started. One button, one LED? It’s almost like LuckFox designed this SBC for Morse! Admittedly we’d prefer an audible output, but adding a buzzer would detract from the purity of this implementation.

He’s had to extend the code, of course, since Samuel Morse did not expect all of the special characters you’re likely to encounter on the terminal. The resultant Programmer’s Morse, or PMorse is a straightforward extension, but [Gabriel] didn’t stop there: he’s also added a set of commands he describes as “vim-like” make using this headless device easier by doing things like deleting whole words or flash the line you’re working on so you can make sure you haven’t made any errors.

If that wasn’t enough, he’s also put an LLM on it. Because in the Year of Our Lord 2026, you apparently cannot escape the frakkin’ toasters by jumping your rag-tag fleet into the 128 MB of RAM on this tiny SBC. Still, his inclusion of Llamma.cpp does add one thing to the project: it can now claim to be the world’s smallest stand-alone chatbot. It’s also the only one that speaks Morse. That’s got to be worth some bragging rights.

[Gabriel] may have a thing for physically tiny Linux devices– his last project, which we featured, was about using Linux on old smartphones with Termux.

Thanks to [Gabriel] for the tip!

Header image credit Luckfox.


hackaday.com/2026/06/02/does-y…

Cybersecurity & cyberwarfare ha ricondiviso questo.

Rilasciati gli attivisti fermati stamattina a Roma
pressenza.com/it/2026/06/rilas…
Dopo oltre 7 ore, le sei persone prelevate dalle Forze dell’Ordine nei pressi dell’Altare della Patria sono state rilasciate dall’Ufficio Immigrazione di Tor Sapienza. A comunicarlo sono state le stesse persone coinvolte una volta uscite dall’edificio, in quanto le comunicazioni…
Extinction Rebellion

reshared this

Cybersecurity & cyberwarfare ha ricondiviso questo.

Sulla proposta del governo italiano di cambiare l’unità di misura “volt” in “volta”:www.terminologiaetc.it/2026/06/01/o... Evidentemente non hanno nulla di meglio da fare!

Proposta del governo: da volt ...

From Scrappy Pallet Wood to Fancy Tea Tray


The media in this post is not displayed to visitors. To view it, please log in.

Pallets are a wonderful way to package goods and move them around, but especially the wooden ones have a very finite lifespan. This means that many of them are discarded every day, even though there is still good wood on them. Even if it’s not the highest quality wood, you can still use it for some nice wooden items, like the tea tray that [GR Woodworking] recently put together.

The reclaimed wood is the typical fast-growing, soft type, with the suspicion of it being paulownia here. Of course, wooden pallets use a wide variety of wood varieties, so not all reclaimed wood is equally suitable for applications like this, and identifying the type can be a challenge in itself.

In the video it’s shown how the wood is planed to make it smooth and straight, before the joints are created and it is married to the poplar or aspen base plate. Of note is that absolutely no power tools or bulky things like router tables are used here, just basic hand tools that should make this kind of woodworking accessible to people even without that kitted-out woodworking shop.

After assembly it’s finished with Vararhana oil-based stain to give it a darker look and really bring out the grain. Naturally, since it’s a tea tray it has to be commissioned with a proper tea ceremony, which it passes with flying colors.

youtube.com/embed/tnNvp0LoJiw?…


hackaday.com/2026/06/02/from-s…

Cybersecurity & cyberwarfare ha ricondiviso questo.

Trump firma un ordine esecutivo che chiede la supervisione dei modelli di intelligenza artificiale

L'ordinanza, che segnalava un passaggio dall'approccio non interventista adottato in precedenza dalla Casa Bianca nei confronti dell'intelligenza artificiale, faceva seguito ai dibattiti su come ottenere il controllo dei modelli di intelligenza artificiale senza compromettere l'innovazione

theguardian.com/us-news/2026/j…

@aitech

reshared this

The 2026 EMF Badge Arrives, With An Add-On. As Expected, It’s Familiar


The media in this post is not displayed to visitors. To view it, please log in.

Four years ago the EMF hacker camp in the UK released a new kind of event badge. The Tildagon was designed to be a recurring event badge, useful for the next EMF rather than destined to be e-waste. With the 2026 event coming up there’s a new Tildagon called the Spaceagon, and as you might expect it’s very familiar indeed.

Tildagon owners can update their badge with the Spaceagon front panel, while those without one can buy the new badge. It has a few minor updates from its predecessor, including better buttons, LEDs, and display mounting, and there’s a compass, a joystick, and touch sensitive areas.

The Tildagon introduced its own add-on format, the Hexpansion. This year there’s the first official Hexpansion, a keyboard, using the same rubber moulding we see on quite a few maker projects. We like the Hexpansion idea because it uses an edge connector rather than a set of pins on the device, but at the cost of more expensive badge parts.

If you’re going to EMF you should be able to order yourself a Spaceagon, or an upgrade kit if you already own a Tildagon. Meanwhile we covered the 2024 version back when it arrived, and surprisingly this isn’t the first keyboard add-on for it either.


hackaday.com/2026/06/02/the-20…

The media in this post is not displayed to visitors. To view it, please log in.

Miasma colpisce Red Hat: 33 pacchetti npm avvelenati per rubare credenziali cloud e segreti CI/CD


@Informatica (Italy e non Italy)
Trentatré pacchetti npm del namespace @redhat-cloud-services sono stati compromessi dalla campagna Miasma, variante evoluta del worm Shai-Hulud. Il malware usa hook preinstall, crittografia AES-GCM e traffico mascherato


Miasma colpisce Red Hat: 33 pacchetti npm avvelenati per rubare credenziali cloud e segreti CI/CD


Trentatré pacchetti npm appartenenti al namespace ufficiale @redhat-cloud-services di Red Hat sono stati compromessi in quello che i ricercatori hanno battezzato la campagna Miasma — una variante evoluta del worm Shai-Hulud già visto colpire l’ecosistema npm. L’attacco ha già contaminato 309 repository GitHub e si è dimostrato capace di sottrarre credenziali di sviluppatori, segreti CI/CD, chiavi SSH e token cloud in modo silenzioso e automatizzato.

Contesto: il worm Shai-Hulud e la famiglia Miasma


Shai-Hulud è emerso come uno dei più sofisticati worm per l’ecosistema npm: combina esecuzione automatica al momento dell’installazione, furto di credenziali multi-target ed esfiltrazione crittografata. La campagna Miasma ne eredita interamente il modus operandi, con alcune innovazioni tecniche — in particolare l’abuso dell’infrastruttura di GitHub e dei servizi Anthropic per staging e fallback di esfiltrazione.

Secondo i ricercatori di Socket, che hanno identificato la campagna, l’attore avrebbe compromesso l’account GitHub di un dipendente Red Hat per pubblicare versioni avvelenate di pacchetti legittimi già ampiamente usati nella toolchain interna di Red Hat Cloud Services. Red Hat ha confermato la rimozione dei pacchetti, precisando che l’impatto era limitato agli strumenti di sviluppo interni — ma la contaminazione di 309 repository GitHub suggerisce una diffusione ben più ampia.

Catena di infezione: dall’npm install alla sottrazione silenziosa


Il meccanismo di innesco è elegante nella sua semplicità: il file package.json dei pacchetti compromessi contiene un hook "preinstall": "node index.js", il che significa che il payload malevolo viene eseguito automaticamente prima che l’installazione del pacchetto si completi — prima ancora che lo sviluppatore possa rendersi conto di cosa sta succedendo.

Il loader di primo stadio utilizza una serie di tecniche di offuscamento: array di char-code, trasformazioni ROT-style e blob cifrati con AES-128-GCM. Una volta deoffuscato, il codice decifra e deposita il payload principale in /tmp/p*.js, lo esegue attraverso Bun (runtime JavaScript ad alte prestazioni) — scaricando silenziosamente Bun da GitHub se non è presente sul sistema.

Il malware esegue quindi una raccolta sistematica di credenziali sensibili, includendo:

  • Segreti GitHub Actions e token npm (~/.npmrc)
  • Credenziali cloud AWS (~/.aws/credentials), GCP, Azure
  • Materiale Kubernetes e HashiCorp Vault
  • Chiavi SSH private (~/.ssh/id_rsa, ~/.ssh/id_ed25519)
  • Credenziali Git (~/.git-credentials, ~/.netrc)
  • Token GitHub CLI via gh auth token

I dati sottratti vengono codificati in Base64, cifrati e inviati via HTTPS POST a un endpoint di esfiltrazione. In caso di fallimento, il malware utilizza un meccanismo di fallback basato su commit GitHub, scrivendo file results–.json in un repository controllato dall’attore — una tecnica dead-drop che sfrutta l’infrastruttura legittima di GitHub per eludere il filtraggio del traffico di rete.

Dettagli tecnici distintivi


Tra gli elementi più caratteristici dell’attacco:

  • Anti-analisi per sistemi russi: il malware verifica la locale di sistema e modifica il comportamento su macchine con lingua russa, suggerendo un attore non russo o comunque attento a evitare incidenti diplomatici.
  • Esfiltrazione verso api.anthropic.com: il traffico di esfiltrazione è mascherato come chiamata alle API Anthropic sulla porta 443, rendendo il traffico praticamente indistinguibile da quello legittimo in ambienti che usano LLM.
  • Commit marker univoco: il codice include la stringa IfYouInvalidateThisTokenItWillNukeTheComputerOfTheOwner e il messaggio di commit Miasma: The Spreading Blight, probabilmente un segno di sfida agli analisti.
  • Tentativo di escalation su CI runner: il malware tenta esecuzione privilegiata via sudo su runner CI, espandendo l’accesso sugli ambienti di build.


Indicatori di compromissione (IoC)

# Pacchetti npm compromessi
@redhat-cloud-services/chrome (v2.3.1 e altre versioni)
@redhat-cloud-services/* (oltre 30 pacchetti nel namespace)

# Artefatti su filesystem
/tmp/p*.js                        # payload principale
/tmp/tmp.0987654321.lock          # file di lock del daemon
b.zip, bun, bun.exe               # runtime scaricato

# File di esfiltrazione fallback
results–.json
results/results–.json

# Endpoint di rete
api.anthropic[.]com:443/v1/api    # esfiltrazione mascherata
api.github[.]com/graphql          # fallback dead-drop
github[.]com/oven-sh/bun/releases/download/bun-v1.3.13/  # staging Bun

# Hash SHA-256
88896d478986d453f5da79b311de39d9b4b1bea95c21af1d8ef181b0f4e52fe9
21b6409a7b84446310daca5409ad6112ac60a1e4bef97736e53fff5f63bfdef4

Attribuzione e collegamento a TeamPCP


L’attribuzione rimane incerta. La disponibilità pubblica del tooling Shai-Hulud ha abbassato la soglia d’ingresso per più attori, rendendo difficile l’attribuzione univoca. I ricercatori notano tuttavia sovrapposizioni tattiche con il gruppo TeamPCP, già collegato ad attività su BreachForums, e con la campagna Mini Shai-Hulud documentata separatamente nello stesso periodo. La scelta di Red Hat come target — un vendor open-source con un ecosistema di sviluppatori ampio e credenziali cloud spesso ad alto privilegio — suggerisce un interesse specifico per l’accesso alle pipeline DevOps enterprise.

Cosa devono fare i difensori


Per i team di sicurezza che gestiscono ambienti con dipendenze npm, le azioni prioritarie sono:

  • Audit immediato di tutti i pacchetti @redhat-cloud-services/* installati nell’ultimo mese, verificando gli hash contro le versioni ufficiali ripristinate.
  • Rotazione preventiva di tutte le credenziali accessibili dagli ambienti di build: npm tokens, chiavi SSH, credenziali AWS/GCP/Azure, segreti GitHub Actions.
  • Blocco dei lifecycle hook npm in ambienti CI/CD tramite la configurazione ignore-scripts=true in .npmrc — questa misura da sola avrebbe impedito l’esecuzione automatica del payload.
  • Monitoraggio anomalo del traffico verso api.anthropic.com e api.github.com da processi node/bun inattesi.
  • Revisione degli hook preinstall in tutti i pacchetti npm di terze parti nel registro privato aziendale.

La campagna Miasma rappresenta un salto qualitativo nell’ingegneria degli attacchi supply chain npm: non si limita a iniettare payload semplici, ma costruisce un’intera infrastruttura di persistenza, esfiltrazione ridondante e anti-analisi che rende difficile sia il rilevamento che la remediation completa.


Cybersecurity & cyberwarfare ha ricondiviso questo.

Can you see how to use a test vector that provides (seed, public key, message, µ, signature) to test a deterministic signing API that does (seed, message) → (signature) or a key generation API that does (seed) → (public key)?

Noted cryptographer D. J. Bernstein can't, certainly in good faith.

*sigh*

I jest, but refuting this FUD takes real resources we could spend so, so, so much better. It'd be sad if it wasn't so harmful.

mailarchive.ietf.org/arch/msg/…

Cybersecurity & cyberwarfare ha ricondiviso questo.

The media in this post is not displayed to visitors. To view it, please go to the original post.

The media in this post is not displayed to visitors. To view it, please go to the original post.

Miasma colpisce Red Hat: 33 pacchetti npm avvelenati per rubare credenziali cloud e segreti CI/CD
#CyberSecurity
insicurezzadigitale.com/miasma…


Miasma colpisce Red Hat: 33 pacchetti npm avvelenati per rubare credenziali cloud e segreti CI/CD


Trentatré pacchetti npm appartenenti al namespace ufficiale @redhat-cloud-services di Red Hat sono stati compromessi in quello che i ricercatori hanno battezzato la campagna Miasma — una variante evoluta del worm Shai-Hulud già visto colpire l’ecosistema npm. L’attacco ha già contaminato 309 repository GitHub e si è dimostrato capace di sottrarre credenziali di sviluppatori, segreti CI/CD, chiavi SSH e token cloud in modo silenzioso e automatizzato.

Contesto: il worm Shai-Hulud e la famiglia Miasma


Shai-Hulud è emerso come uno dei più sofisticati worm per l’ecosistema npm: combina esecuzione automatica al momento dell’installazione, furto di credenziali multi-target ed esfiltrazione crittografata. La campagna Miasma ne eredita interamente il modus operandi, con alcune innovazioni tecniche — in particolare l’abuso dell’infrastruttura di GitHub e dei servizi Anthropic per staging e fallback di esfiltrazione.

Secondo i ricercatori di Socket, che hanno identificato la campagna, l’attore avrebbe compromesso l’account GitHub di un dipendente Red Hat per pubblicare versioni avvelenate di pacchetti legittimi già ampiamente usati nella toolchain interna di Red Hat Cloud Services. Red Hat ha confermato la rimozione dei pacchetti, precisando che l’impatto era limitato agli strumenti di sviluppo interni — ma la contaminazione di 309 repository GitHub suggerisce una diffusione ben più ampia.

Catena di infezione: dall’npm install alla sottrazione silenziosa


Il meccanismo di innesco è elegante nella sua semplicità: il file package.json dei pacchetti compromessi contiene un hook "preinstall": "node index.js", il che significa che il payload malevolo viene eseguito automaticamente prima che l’installazione del pacchetto si completi — prima ancora che lo sviluppatore possa rendersi conto di cosa sta succedendo.

Il loader di primo stadio utilizza una serie di tecniche di offuscamento: array di char-code, trasformazioni ROT-style e blob cifrati con AES-128-GCM. Una volta deoffuscato, il codice decifra e deposita il payload principale in /tmp/p*.js, lo esegue attraverso Bun (runtime JavaScript ad alte prestazioni) — scaricando silenziosamente Bun da GitHub se non è presente sul sistema.

Il malware esegue quindi una raccolta sistematica di credenziali sensibili, includendo:

  • Segreti GitHub Actions e token npm (~/.npmrc)
  • Credenziali cloud AWS (~/.aws/credentials), GCP, Azure
  • Materiale Kubernetes e HashiCorp Vault
  • Chiavi SSH private (~/.ssh/id_rsa, ~/.ssh/id_ed25519)
  • Credenziali Git (~/.git-credentials, ~/.netrc)
  • Token GitHub CLI via gh auth token

I dati sottratti vengono codificati in Base64, cifrati e inviati via HTTPS POST a un endpoint di esfiltrazione. In caso di fallimento, il malware utilizza un meccanismo di fallback basato su commit GitHub, scrivendo file results–.json in un repository controllato dall’attore — una tecnica dead-drop che sfrutta l’infrastruttura legittima di GitHub per eludere il filtraggio del traffico di rete.

Dettagli tecnici distintivi


Tra gli elementi più caratteristici dell’attacco:

  • Anti-analisi per sistemi russi: il malware verifica la locale di sistema e modifica il comportamento su macchine con lingua russa, suggerendo un attore non russo o comunque attento a evitare incidenti diplomatici.
  • Esfiltrazione verso api.anthropic.com: il traffico di esfiltrazione è mascherato come chiamata alle API Anthropic sulla porta 443, rendendo il traffico praticamente indistinguibile da quello legittimo in ambienti che usano LLM.
  • Commit marker univoco: il codice include la stringa IfYouInvalidateThisTokenItWillNukeTheComputerOfTheOwner e il messaggio di commit Miasma: The Spreading Blight, probabilmente un segno di sfida agli analisti.
  • Tentativo di escalation su CI runner: il malware tenta esecuzione privilegiata via sudo su runner CI, espandendo l’accesso sugli ambienti di build.


Indicatori di compromissione (IoC)

# Pacchetti npm compromessi
@redhat-cloud-services/chrome (v2.3.1 e altre versioni)
@redhat-cloud-services/* (oltre 30 pacchetti nel namespace)

# Artefatti su filesystem
/tmp/p*.js                        # payload principale
/tmp/tmp.0987654321.lock          # file di lock del daemon
b.zip, bun, bun.exe               # runtime scaricato

# File di esfiltrazione fallback
results–.json
results/results–.json

# Endpoint di rete
api.anthropic[.]com:443/v1/api    # esfiltrazione mascherata
api.github[.]com/graphql          # fallback dead-drop
github[.]com/oven-sh/bun/releases/download/bun-v1.3.13/  # staging Bun

# Hash SHA-256
88896d478986d453f5da79b311de39d9b4b1bea95c21af1d8ef181b0f4e52fe9
21b6409a7b84446310daca5409ad6112ac60a1e4bef97736e53fff5f63bfdef4

Attribuzione e collegamento a TeamPCP


L’attribuzione rimane incerta. La disponibilità pubblica del tooling Shai-Hulud ha abbassato la soglia d’ingresso per più attori, rendendo difficile l’attribuzione univoca. I ricercatori notano tuttavia sovrapposizioni tattiche con il gruppo TeamPCP, già collegato ad attività su BreachForums, e con la campagna Mini Shai-Hulud documentata separatamente nello stesso periodo. La scelta di Red Hat come target — un vendor open-source con un ecosistema di sviluppatori ampio e credenziali cloud spesso ad alto privilegio — suggerisce un interesse specifico per l’accesso alle pipeline DevOps enterprise.

Cosa devono fare i difensori


Per i team di sicurezza che gestiscono ambienti con dipendenze npm, le azioni prioritarie sono:

  • Audit immediato di tutti i pacchetti @redhat-cloud-services/* installati nell’ultimo mese, verificando gli hash contro le versioni ufficiali ripristinate.
  • Rotazione preventiva di tutte le credenziali accessibili dagli ambienti di build: npm tokens, chiavi SSH, credenziali AWS/GCP/Azure, segreti GitHub Actions.
  • Blocco dei lifecycle hook npm in ambienti CI/CD tramite la configurazione ignore-scripts=true in .npmrc — questa misura da sola avrebbe impedito l’esecuzione automatica del payload.
  • Monitoraggio anomalo del traffico verso api.anthropic.com e api.github.com da processi node/bun inattesi.
  • Revisione degli hook preinstall in tutti i pacchetti npm di terze parti nel registro privato aziendale.

La campagna Miasma rappresenta un salto qualitativo nell’ingegneria degli attacchi supply chain npm: non si limita a iniettare payload semplici, ma costruisce un’intera infrastruttura di persistenza, esfiltrazione ridondante e anti-analisi che rende difficile sia il rilevamento che la remediation completa.


Linux Fu: Taming Strace


The media in this post is not displayed to visitors. To view it, please log in.

While many operating systems seem to try to prevent you from peeking under the hood, Unix and Linux positively encourage it. One great tool that we’ve looked at before is strace. Using this tool, you can see details about every system call a program makes. As you might imagine, for any significant program, the output from strace can be huge.

While I’m not always a fan of GUIs, this is one of those cases where making the data easier to browse is a great idea. Enter strace-tui, a text-based GUI for strace from [Rodrigodd]. The program can parse output from strace or manage the strace execution itself, and either way, display the data in a useful way.

I started out looking at [janestreet’s] strace_ui, but the OCaml setup was throwing errors for me, so I just gave up. The strace-tui installs like many Rust programs, using cargo, and it went smoothly.

An Example

The strace-tui interface.
The only issue I had running the tool was that I don’t normally keep ~/.cargo/bin on my path. You can add it to your path, link the executable into your path, or solve that in any number of other ways.

As an example, I traced a symbolic link command (ln -sf nature.txt test.link). It is easy to pick out some essential information on the top line. The command took 112 system calls, 14 of them failed (which isn’t unexpected), there were no unfinished calls, no signals, and only a single PID.

The bottom shows things you can do. Arrows or j and k, along with the usual cursor control keys like Home and Page Down scroll through the list. The right and left arrows will expand or collapse items. That will show details about the call in question, including the arguments and return values. You can consult the help for all the details.

Useful Tools


The real power, though, lies in filtering out the noise and searching for specific things. If you are looking at something you don’t want to see, you can press a lowercase h to hide it, but note that it hides everything similar, not just an individual line. An uppercase H will bring up a filter dialog where you can include or exclude groups of data.

Searching is also a great way to find what you want. A slash key starts a search. The N key navigates with a lowercase entry moving forward and an uppercase one moving backward.

For example, if I only wanted to look at openat commands, I could open the dialog. Not only does it show filters, but it also shows how many things match (there are 30 instances of openat). Pressing a will toggle all entries off and then selecting openat greatly reduces the amount of output. I also selected symlinkat, read, and fstat so I would only look at the file-related items.
Peeking at the system call that does the actual linking.
Many of the file operations are related to loading shared libraries and locales. To find the actual line that makes the link, it was easy to press the slash key and some text from the file like test.link.

That will highlight the symlinkat line, which is no surprise, but this is a simple example. If you press Enter or the right arrow, you can see more detail, including arguments, the return value, the amount of time executing, and a backtrace that shows how your program made it to the call.

This is a simple example, but the program can also visualize multi-threaded or multi-process traces using graphs. That can be helpful for analyzing real programs.

Even this simple program has a lot of output. Sure, if you are trying to debug a locale-related problem, all of the lines about loading locale files that don’t exist might be gold. But most of the time, you don’t really care about all the standard loading scaffolding and a tool like this can help cut through the chatter.

Missing Links


According to the project page, there are some missing features, and we presume this is a roadmap for future development.

In particular, the program can’t filter traces for specific processes or threads. There’s also no way to copy details to the clipboard or export filtered traces out to a file. Of course, it is open source, so you can always volunteer to add some of this or your favorite feature.

If you give strace-tui a shot, or have other strace tips and tricks you’d like to share, let us know in the comments.


hackaday.com/2026/06/02/linux-…

Cybersecurity & cyberwarfare ha ricondiviso questo.

The media in this post is not displayed to visitors. To view it, please go to the original post.

Altre 150 aziende nel progetto Glasswing! Energia, servizi idrici, sanità, hardware

📌 Link all'articolo : redhotcyber.com/post/altre-150…

A cura di Redazione RHC

#redhotcyber #news #intelligenzaartificiale #sicurezzainformatica #partnership #cybersecurity

Cybersecurity & cyberwarfare ha ricondiviso questo.

#Instagram Account Hijacks Expose the Security Risks of #AI-Powered Support
securityaffairs.com/193034/hac…
#securityaffairs #hacking
in reply to securityaffairs

Greetings!

Checked your product earlier and honestly it feels like something Reddit users would naturally talk about because the underlying problem already gets discussed there often.
But right now there’s almost no visibility around your brand itself yet.
Just wondering, are you mainly relying on SEO and ads currently?
I think people on reddit would actually discuss this

Cybersecurity & cyberwarfare ha ricondiviso questo.

The media in this post is not displayed to visitors. To view it, please go to the original post.

Gli hacker criminali colpiscono Carnival. 6 milioni le persone esposte

📌 Link all'articolo : redhotcyber.com/post/gli-hacke…

A cura di Luigi Zullo

#redhotcyber #news #cybersecurity #hacking #violazionedeidati #databreach #sicurezzainformatica

STM32 Handheld Has OpenGL and all the Classics


The media in this post is not displayed to visitors. To view it, please log in.

We do sometimes go on about how absurdly powerful microcontrollers are these days, but this time it’s technically a microprocessor, not a microcontroller, at the heart of the build — specifically, an STM32MP2. Still, you know you’re living in the future when an STM32 of any sort can not only run [John Cronin]’s gk handheld game console, but provide 3D acceleration to boot.

Full disclosure: you’ve seen this handheld here before — sorta. That was version 3, which was an STM32-based handheld. V3 used the much less powerful STM32H7S7L8, with a single Cortex-M7 clocked at 600 MHz and a 2D NeoChrom GPU. The STM32MP2, by contrast, has dual Cortex-A35 cores running 1.5 GHz and a bonus Cortex-M33. It’s running a custom OS called gkos, which is mostly POSIX-compliant and boasts nigh-instantaneous boot times.

As with the last version, you can run a bevy of emulators from the 8-bit to the 32-bit era, but the added power and OpenGL support mean this handheld also runs N64 games via a fork of mupen64. There are also emulators for ‘real’ computers, namely Atari ST and XL, and a little-known thing known as a “PC”. DOSBox gets the equivalent performance of a 50 MHz 486, which means you can run all the classics, including DOOM, though that will be more performant running the native-running port of sdl-DOOM.

You also get extra inputs to play with and a bigger screen compared to the last version. Oh, and WiFi. There are accelerometers for tilt control, and did we mention the screen’s touch input is supported? If it weren’t for the form-factor, we’d call this a capable little computer. The GK handheld looks like an awesome handheld console, check it out in the demo video below.

youtube.com/embed/HnWTx0CX4E8?…


hackaday.com/2026/06/02/stm32-…

Cybersecurity & cyberwarfare ha ricondiviso questo.

Russia's intel agency FSB says they found a spyware attack against "high-ranking" government officials carried out by foreign intelligence agencies.

"Using the technical capabilities of large international IT corporations and mobile communications, representatives of foreign intelligence agencies carried out covert, unauthorized collection of various types of information from the devices of cyberattack targets." [Google Translation]

web.archive.org/web/2026060212…

reshared this

Cybersecurity & cyberwarfare ha ricondiviso questo.

The media in this post is not displayed to visitors. To view it, please go to the original post.

Vulnerabilità nel plug-in Kirki: migliaia di siti WordPress a rischio

📌 Link all'articolo : redhotcyber.com/post/vulnerabi…

A cura di Carolina Vivianti

#redhotcyber #news #cybersecurity #hacking #wordpress #kirki #vulnerabilita #CVE20268206

Cybersecurity & cyberwarfare ha ricondiviso questo.

U.S. #CISA adds #Oracle #WebLogic flaw to its Known Exploited Vulnerabilities catalog
securityaffairs.com/193027/sec…
#securityaffairs #hacking
Cybersecurity & cyberwarfare ha ricondiviso questo.

Oggi celebriamo una data fondamentale per la nostra storia: il 2 giugno 1946, quando il popolo italiano fu chiamato a scegliere tra monarchia e repubblica ma il 2 giugno è anche una data simbolica per un altro motivo storico di enorme importanza: fu la prima volta che le donne italiane votarono in una consultazione politica nazionale.
Milioni di donne andarono alle urne non solo per esprimere il loro voto, ma anche per essere elette. 21 di loro entrarono nell’Assemblea Costituente, ..
🔽

Jenny’s Daily Drivers: Microsoft Windows 11


The media in this post is not displayed to visitors. To view it, please log in.

In our search for the unusual or interesting among the world of operating systems, it might seem unexpected that today’s choice for a Daily Driver is the latest version of Microsoft Windows. Aside from Hackaday perhaps having a larger than average percentage of viewers using Linux based operating systems and generally catering to open source enthusiasts, there’s hardly anything special about Windows, is there?

Oddly for me there is — because while it’s a common enough OS for the masses, the last time I had a Windows computer it ran XP. That venerable OS is a world away from today’s Windows 11, and thus as someone who’s exclusively sat in front of a GNOME desktop for much of the last two decades, it’s an entirely new operating system.

There’s no doubt that it will make a Daily Driver, because of course I’ll be able to do my work on it. Where the interest lies is in seeing what Windows has become. Is it still a useful general purpose operating system, or has it become the locked-down walled garden of crapware that its detractors warn you about? Time to dive in.

A Secret Windows Machine


I have had a Windows partition on this machine since I bought it back in 2024. It’s an ex-corporate laptop from a reseller, and those machines always come with a too-small flash drive and a Windows install. So when I bought a new much larger drive for my Linux install I dropped the Windows partition on it too. After all, you never know when you might need Windows for something, right? Two years later and I’ve never touched it, so my first task in my Windows 11 is to run a system update. I timed the start to 16:30, and left it running. I have a gigabit fibre connection so it should be quick, shouldn’t it. At 19:16 I was finally able to use the computer, but even then Microsoft wasn’t quite finished. There were a slew of permissions choices where I had to opt out of their various data slurps, and their offers and mail.

Coming back to the Windows desktop when your last experience was XP with the Windows 95 theme is a bit of a shock. You instinctively head for the Start menu in the bottom left corner and instead find a widget box full of news feeds and stock tickers you don’t want. Closer inspection shows they’ve chased a macOS style interface with a Windows logo on the bottom bar as the Start menu roughly where Mac users find their folder full of apps.

I’m trying to approach this think as a Windows user would, so instead of heading off and downloading open source installers as you might expect, I’m off to the Microsoft Store. Although Redmond has its hand on my shoulder I was able to find GIMP without issue, so the basic requirements for my normal daily use is sorted without any drama at all. It’s the ancient version 2.1 though, so it was off to gimp.org for the latest version. Installation was the same as any Windows install back in the day, there’s no locking down here.

Crapware’s a Bit Different


So I’ve got a Daily Driver, what are my impressions. After so long away and having missed the debacle of Windows 8’s Metro interface, I think the desktop interface is actually pretty good. It’s kept up with the times in a way macOS — with its barmy top-corner menus which just don’t work in a world of 4K screens — hasn’t. As to the commercial aspects of the OS, I was expecting it to ask me for a Microsoft account and it hasn’t, so that’s a plus. But the thing I had forgotten about was the ubiquity of nag screens. I haven’t had to click a “No, I don’t want to upgrade to your premium version” button in a very long time, and here I am suddenly having all manner of software wanting my attention. No Adobe Acrobat, I don’t want to give you any money! And then there’s the AI. Nothing in my Linux install is trying to offer me AI services, but it seems everything is here.

My jaunt into Windows land will be over when I’ve finished writing this piece, and I guess it’ll be as long again before I revisit this partition. Updating it took nearly three hours, and it’s constantly nagging me for paid upgrades, offering me news stories from sources I don’t like, and trying to push AI services on me. But is it a walled garden of crapware? That’s a more difficult question to answer. I’ve not had to enter a Microsoft account to use it, and I can install the software I want, so it’s not become the walled garden its detractors will tell you it has. The crapware though? Less clear cut.

This is a reseller laptop, so at least in theory, its original drive should have been wiped or even destroyed as part of a corporate data security scheme. So the reseller puts a cheap drive in and gives it a basic Windows install. It’s completely vanilla Windows 11, which is where it differs from many new laptops. There is no bundled software, no nagware, no commercial anti-virus, and no dubious-value security package. It’s as clean as Windows gets, but even so, there’s still too many features being pushed on me that I simply don’t want. It may not have old-style crapware installed, but the crap is still there.

So my final impression? This trip into Windows-land has been interesting, and I’ve found an OS better than I expected. But it’s reminded me again of the reasons why I moved on from dual-booting Windows XP all those years ago, with a lingering feeling that I still don’t quite own it.

Windows 11 then, it’s a daily driver for millions of people, but I still won’t be one of them.


hackaday.com/2026/06/02/jennys…

Cybersecurity & cyberwarfare ha ricondiviso questo.

The media in this post is not displayed to visitors. To view it, please go to the original post.

Indice dei miei Post Tossici

Consigli di follow



Riflessioni tossiche sul Fediverso



Consigli per gli acquisti



Buongiorno.

Inauguro i #consiglidifollow, suddivisi per argomento.
Non sono elenchi esaustivi. Semplicemente condivido gli account che mi è capitato d'incontrare per caso e che piacciono a me.

Primo elenco: Letteratura.


(Aggiornamento 9 maggio 2026)

@Bibliothecaris
@cctmwebsite
@differx@mastodon.uno
@differx@poliverso.org
@Fbrzvnrnd
@FilippoBiagioli
@giuliocavalli
@gutenberg_new
@huss
@internetarchive
@jeffjarvis
@libri@feddit.it
@libri@poliverso.org
@lisavag
@lucianofloridi
@m
@overholt
@Ricciotto
@TGioiellieri
@Umbertogaetani
@viadellabarca
@WedaleBooks
@WeirdWriter


Questa voce è stata modificata (23 ore fa)
in reply to ッ AnMus

@anonimo_musichiere Grazie. Mi sono accorto che la ricerca per hashtag è meno efficace di quanto sperassi, perciò ho creato quest'indice nell'ottica di costruire io il Fediverso così come mi piace e l'ho fissato in cima ai miei post.

Ben lungi da me volere diventare un punto di riferimento, piuttosto spero di indurre qualcuno in più a riflettere sulla reale tossicità di alcune dinamiche che si sono venute a creare qui nel Fediverso e a contribuire a seppellirle sotto a un'immensa quantità di materiale virtuoso.


Riflessioni tossiche sul Fediverso.

Quarta puntata.


Oggi intendo fare un discorso un po' più complesso. Inizierò raccontando di come venni a conoscenza del Fediverso.

Era il 2022.

Il mio social preferito, Twitter, pretendeva di farmi partecipare al controllo della veridicità delle notizie lì pubblicate. Mi sembrava ridicolo che chiedesse aiuto a me anziché provvedere a controllare attraverso i propri dipendenti. Con tutti i soldi che prendeva dagli sponsor...

Uno dei fondatori se n'era andato. Annunciava di volere ricreare il social delle origini, diverso dall'attuale che si era troppo riempito di pubblicità e che si dimostrava poco attento ai gusti dei propri utenti. Tuttavia i mesi passavano, il nuovo social tardava a nascere, mentre Twitter continuava a peggiorare.

Sempre più spesso leggevo di un altro nuovo social, il quale presentava però la complessità di essere suddiviso in tanti server diversi, che curiosamente si chiamavano istanze. Dicevano che iscrivendosi a una qualsiasi istanza si sarebbe potuto poi comunicare con tutte le altre. Gli articoli parlavano talvolta di “Mastodon” e talvolta di “Fediverso”, non avevo ancora capito bene se si trattasse della stessa cosa.

Dicevano che bisognasse scegliere bene a quale istanza iscriversi. Circolavano elenchi d'istanze, ognuna con le sue peculiarità: alcune molto politicizzate, altre generaliste, altre più tematiche.

Cominciai a pensare d'iscrivermi, ma per farlo avrei dovuto innanzitutto scegliere un'istanza. In quelle generaliste preferivo non entrare perché ero deluso dal generalista Twitter. Quelle politicizzate mi sembravano troppo vincolanti. Per esclusione ne scelsi una fondata da un musicista e nata per fare cultura, scambiarsi impressioni sulle proprie attività del tempo libero, magari sulle proprie letture. Mi c'iscrissi e cominciai a pubblicare i link a ciò che leggevo, cioè articoli da cui capire che direzione stesse prendendo il mondo. Alcuni di essi parlavano di guerre. Dopo pochi giorni, un moderatore mi chiese di nasconderli dietro a un Content Warning per non disturbare chi parlava di videogiochi.

Videogiochi?!?

Guardai meglio la timeline locale, mi resi conto che in istanza si parlava soprattutto di quelli. Come avevo fatto a non accorgermi che il suo misterioso nome, Livello Segreto, si riferiva ai livelli dei videogiochi?

Avevo sbagliato istanza. Per fortuna gli account si possono trasferire. Una sera decisi di trasferirmi in un'istanza per giornalisti1. Feci la domanda d'iscrizione spiegando che, sebbene non fossi un giornalista, mi piaceva pubblicare link ad articoli. Con mia grande emozione, venni accettato in Poliversity.it e mi ci trasferii.

Gli articoli che leggevo riguardo a Mastodon spiegavano che ci si dovesse costruire la propria timeline seguendo i giusti account. Quando gli account seguiti divennero tanti, costruii più timeline diverse organizzando gli account per argomento attraverso le liste. Nacquero così esattamente le liste che ogni tanto condivido nei “Consigli di Follow”. Anche ai bei vecchi tempi di Twitter mi piaceva condividere liste di account.

§

Fatta questa premessa, eccomi finalmente alla parte tossica del discorso.

Essere presenti nel Fediverso non è solo costruirsi la propria timeline attraverso un'oculata scelta di chi si segue. O le proprie timeline attraverso la suddivisione in liste.

Non è neanche pubblicare ogni tanto qualcosa per farsi sentire, nemmeno se quel qualcosa ci sta a cuore.

Essere presenti è innanzitutto scegliere con cura l'istanza in cui stare, affinché sia affine ai nostri interessi e dica così qualcosa di noi.

In tanti perdono entusiasmo perché non condividono le scelte dei propri admin d'istanza. Cambiate istanza, sceglietene una che vi assomigli e che vi dia gli strumenti di cui avete bisogno.

Cambiate istanza! È inutile restare in un'istanza basata sulla piattaforma Mastodon se si pubblicano prevalentemente fotografie, così com'è sciocco creare di continuo fastidiose catene di post (i thread) quando si può scegliere un'istanza che consenta post più lunghi.

E, dopo aver scelto bene l'istanza, se abbiamo un'idea di che cosa ci piace diamoci da fare per crearla: costruiamo noi il Fediverso così come ci piace!

§

Come sempre concludo con gli hashtag che voglio appiccicare a questo post: #riflessionitossiche, #istanze e #CostruiamoIlFediverso. E cito la comunità @fediverso perché è moderata dallo stesso admin dell'istanza in cui mi trovo.

Arrivederci alla prossima Riflessione Tossica.

1 Che poliversity.it fosse “per giornalisti” è stato un mio pregiudizio: com'è scritto in descrizione, «l'istanza è focalizzata sull'ambiente accademico, scientifico, scolastico e su quello dell'informazione e del giornalismo. In un momento in cui la cultura scientifica e il mondo dell'informazione sembrano assediati dalla disinformazione, le fake news e il pensiero magico, Poliversity vorrebbe diventare una sorta di piazza accademica del Fediverso italiano per la promozione dell'incontro tra conoscenza e informazione».


Cybersecurity & cyberwarfare ha ricondiviso questo.

Sempre più convinto di ciò che Stephen #Hawking affermava con fermezza:

“Il più grande nemico della #conoscenza non è l'ignoranza, ma è l'illusione della conoscenza”

Cybersecurity & cyberwarfare ha ricondiviso questo.

@Nico_Piro@mastodon.uno Vietato criticare #Israele; vietato criticare la #guerra in generale. Avviene a un giornalista noto, per intimidire gli ignoti: nicopiro.substack.com/p/2-giug…
Unknown parent

mastodon - Collegamento all'originale

OrionBelt©

@Otttoz vero assolutamente! ci vorrebbe anche in un mondo più empatico,che si sfanculassero in massa sti social(...)mente basati su algoritmi di profilazione
a scopo di lucro e per me anche irrispettosi della costruzione del nostro paese che però già da un po e inchinato a 90° nei confronti di.... poi c'è il detto"si dice il peccato e non il peccatore"ma qui non funziona così--->😁😁😆: google , meta,microsoft,amazon,x &co...)

Wardriving assessment across Mexico: Preparing for the 2026 World Cup


The media in this post is not displayed to visitors. To view it, please log in.


Introduction


Mexico is one of the host countries for the 2026 FIFA World Cup, with matches to be played in three major cities: Mexico City, Monterrey, and Guadalajara. These locations are expected to see a large influx of international visitors, increasing the potential security risks. Many of those risks arise from users connecting to public wireless networks.

To better understand the wireless environments that visitors may encounter, we at Kaspersky GReAT conducted a wardriving assessment in the three host cities. The aim of the study was to analyze characteristics, deployment patterns, security configurations and potential exposure risks of public Wi-Fi infrastructure in urban wireless environments.

The information collected during the assessment was used exclusively for passive observation and infrastructure analysis. No attempts were made to authenticate, intercept communications, exploit systems or interact with the detected wireless networks beyond the publicly broadcast management information.

During processing of the collected data, one step involved filtering out networks belonging to cars or cell phones categorized as mobile hotspots because they do not represent networks that can be considered part of the assessment.

Research scope


The cities included in the study have high population density and extensive wireless infrastructure deployments. We chose areas with the most prominent wireless network activity and highly concentrated public access points. We carried out wardriving research in Monterrey back in 2008, but the city’s hotspot landscape has changed since then.

We chose the following analysis areas for each of the cities:

  1. Mexico City: México City Stadium, Mexico City International Airport, Zócalo, Paseo de la Reforma, Colonia Roma, La Condesa, Polanco, and Coyoacán.
  2. Guadalajara: Guadalajara Stadium, Guadalajara International Airport, the city center, Zapopan, Providencia, Avenida Chapultepec, Colonia Americana, Tlaquepaque, and the area around Andares.
  3. Monterrey: Monterrey Stadium, Monterrey International Airport, Fundidora Park, Cintermex Monterrey, the downtown area, Barrio Antiguo, MacroPlaza, and the San Pedro financial district.

The wireless information was collected using passive wireless reconnaissance techniques. The collected information included:

  • SSID analysis and information exposure, including BSSID-derived SSIDs
  • Default router configurations and ISP deployments
  • Frequency and signal characteristics
  • Channel congestion and spectrum usage
  • Wireless security configurations, including:
    • Open and insecure wireless networks
    • WPS-enabled networks
    • Secure networks (WPA2/WPA3) with WPS enabled


We performed a wireless infrastructure analysis in Mexico City, Guadalajara, and Monterrey. We drove through the areas surrounding the World Cup stadiums, tourist zones, and other places where fan concentrations are likely to be largest. Our goal was to evaluate the security status, deployment characteristics and operational exposure of detected wireless networks.

In total, we recorded 84,588 signals with 69,473 unique Service Set Identifiers (SSIDs) in busy locations and World Cup zones across the three cities. Mexico City accounted for 61.4% of the signals, Guadalajara for 23.6%, and Monterrey for 14.8%. Approximately 82% of the signals had a single SSID (81.9%, 81.34%, and 84% respectively). Notably, they all operate under the IEEE 802.11 standard protocol.

Particular attention was given to identifying standard deployment patterns, legacy configurations, default vendor settings and information disclosure through publicly broadcast wireless identifiers.

The following sections present the results that were obtained by analyzing wireless infrastructure across the three locations.

Our findings

SSID analysis and information exposure


SSID analysis was conducted to evaluate naming conventions, deployment standardization and potential information exposure.

Only a few networks (0.0047%) have an invisible SSID, meaning the names of these networks are not broadcast. Some users prefer to hide the SSID for various reasons, such as the network’s purpose, the profile of its users, internal policies, etc. In contrast, the rest of the networks maintained active SSID broadcasting.

SSID structures may unintentionally disclose operational details about internet service providers (ISPs), device manufacturers, deployment practices, organizational ownership or user identity. The repeated presence of default SSID naming patterns across the analyzed locations indicates a significant degree of infrastructure homogeneity and reuse of default wireless configurations. It may also facilitate passive infrastructure profiling by revealing standard characteristics in use.

Approximately 34% of the detected networks retained the default SSID naming conventions provided by the manufacturer or ISP, while 66% used customized identifiers.

Distribution of SSID naming conventions (download)

Several recurring SSID naming conventions associated with ISP-provided deployments were identified in the three cities. The most frequently observed patterns include identifiers such as “Club_Totalplay_WiFi”, “izzi WiFi”, and “Megacable WiFi”, which suggests extensive standardization of wireless infrastructure deployment. Additionally, we observed distinctive location-specific SSIDs in each area of analysis, such as “XXXX-Internet para Todos-CDMX” or “RED JALISCO”.

Most frequently observed SSID patterns (download)

Sequential SSID naming structures were also identified during the analysis. Patterns such as “INFINITUMXX” and “IZZI-XX” suggest automated ISP deployment and large-scale deployment strategies.

We identified 33 unique sequential naming structures among the 137 sequential SSIDs in total, representing approximately 0.16% of the detected wireless networks.

The following graph shows the top five sequential SSID patterns found in the largest number of networks:

Five most frequently observed sequential patterns (download)

Several customized SSIDs contained personal or organizational identifiers, including family names, professions, addresses or internal department references. Although personalized SSIDs may simplify local network identification for users, they may also expose sensitive information that could be useful for social engineering, physical targeting, or organizational profiling.

BSSID-derived SSID


During the analysis, multiple networks were identified that used the physical MAC address of a Wi-Fi access point (BSSID) as the visible SSID. This practice exposes hardware-level information that could facilitate vendor fingerprinting and targeted reconnaissance activities.

The organizationally unique identifier (OUI) contained in the first bytes of the BSSID identifies the equipment manufacturer. Threat actors can correlate exposed manufacturers with device-specific vulnerabilities.

BSSID-derived SSID by city (download)

Notably, we found that more than 30% of networks in all three cities reuse the MAC address as the SSID.

Default router configurations and ISP deployments


We performed wireless infrastructure profiling to identify the most common wireless equipment manufacturers and ISP deployments across the three locations.

Large-scale ISP deployments frequently use standardized wireless configurations and vendor-specific hardware platforms. Identifying dominant manufacturers and ISP naming conventions can provide insight into infrastructure and deployment practices facilitating the mapping of standardized attack surfaces.

The following figure shows the distribution of the most commonly used manufacturers.

Most frequently observed wireless equipment manufacturers (download)

The manufacturer analysis revealed a strong concentration of wireless infrastructure among a limited number of vendors. Across the three locations, Huawei Technologies, MediaTek-based devices, and other manufacturers’ equipment that is distributed through ISP channels represented a significant portion of the detected deployments. Mexico City had the most diverse infrastructure, while Monterrey and Guadalajara had a greater concentration of wireless equipment known as SOHO (small office/home office) or residential-grade hardware. The widespread presence of standard vendor platforms may facilitate infrastructure fingerprinting and large-scale targeting of known device-specific vulnerabilities.

Most frequently observed wireless equipment manufacturers across the three cities (download)

ISP deployments frequently exhibited standardized configuration patterns and recurring manufacturer identifiers. Our ISP deployment analysis revealed a high concentration of access points associated with major residential internet providers. Deployments associated with Infinitum, Totalplay and Izzi represented a substantial portion of the detected wireless infrastructure across all locations. These findings suggest a high degree of deployment standardization across networks associated with major residential internet providers. This observation was supported by the repeated presence of ISP-associated SSIDs such as “Infinitum”, “Totalplay”, and “Izzi”, combined with manufacturer identifiers frequently associated with consumer equipment, including Huawei, ZTE and other residential wireless equipment vendors.

It is important to note that, for this analysis, ISPs were primarily inferred from SSID naming conventions and manufacturer fingerprint data. A significant portion of the detected wireless networks fell into the “UNKNOWN/CUSTOM” category. This classification includes custom hotspots and networks whose naming conventions did not expose identifiable ISP-associated patterns. The findings suggest that many users and organizations (as we saw previously, approximately 66%) use custom network names, limiting direct provider attribution.

The following figure illustrates the distribution of ISP-associated wireless deployments in general.

Most frequently observed ISPs (download)

To better understand this distribution, we took the most frequently observed ISPs by city.

Most frequently observed ISPs across the three cities (download)

Frequency and signal characteristics


We also analyzed wireless signal characteristics to evaluate coverage quality, signal strength, and frequency band utilization in the three cities. In dense urban environments, signal quality and frequency spectrum distribution can affect wireless reliability, client connectivity, roaming performance, and overall network efficiency.

Signal quality analysis revealed that a substantial portion of the detected access points operated under weak or very weak signal conditions. Monterrey had the highest percentage of very weak signals, with approximately 50% of detected deployments. Similar patterns were observed in Guadalajara and Mexico City, suggesting high-density wireless environments with overlapping coverage areas. Only a limited percentage of networks were classified within the very good or excellent signal categories across the three locations.

Signal quality distribution by city (download)

Signal stability analysis revealed that most detected wireless deployments exhibited stable beacon transmission behavior. More than 96% of the detected access points across all locations were classified as stable, while only a small percentage exhibited unstable or indeterminate signal behavior.

These findings imply that the majority of the wireless infrastructure observed during the assessment corresponded to permanently deployed access points rather than transient or intermittent wireless devices.

Signal stability status (download)

Frequency band analysis revealed the strong prevalence of 2.4 GHz wireless deployments across the three locations. More than 95% of the detected wireless networks operated within the 2.4 GHz spectrum, while only a small percentage of deployments were classified under the unknown or non-standard frequency categories. This uneven distribution reflects the continued prevalence of legacy-compatible wireless infrastructure and SOHO deployments.

Frequency band utilization (download)

These findings are consistent with dense urban wireless environments with large numbers of access points in restricted spectrum allocations.

Channel congestion and spectrum usage


Next, we analyzed wireless channel utilization to evaluate frequency spectrum congestion and channel allocation patterns across the three cities. Our analysis focused on the 2.4 GHz spectrum, where channel overlap and high access point density commonly produce interference and degraded wireless performance. In densely populated wireless environments, an excessive concentration of access points on a limited number of channels can lead to co-channel interference, packet collisions, reduced throughput, and degraded network stability.

Spectrum congestion analysis revealed that the 2.4 GHz band consistently experienced elevated congestion levels across the three cities. The detailed results showed a strong concentration of deployments on channels 11, 6 and 1, which are traditionally recommended as non-overlapping channels within the 2.4 GHz spectrum. Channel 11 was the most utilized channel, accounting for 25.2% of the detected access points, followed by channel 6 with 22.5% and channel 1 with 19.5%. This distribution indicates that most wireless deployments adhere to standard channel allocation practices for 2.4 GHz Wi-Fi environments.

The following figure illustrates the overall distribution of the most frequently utilized wireless channels.

Most utilized wireless channels (download)

To further assess wireless spectrum saturation, the detected access points were grouped according to channel congestion levels: VERY_HIGH, HIGH, UNKNOWN, MEDIUM, LOW and NONE.

Mexico City had the highest proportion of heavily congested wireless channels, with approximately 7% of detected access points operating under HIGH congestion conditions. Guadalajara followed with nearly 5% of deployments categorized as HIGH congestion, while Monterrey had the lowest percentage at approximately 3.29%.

These findings suggest that wireless spectrum saturation increases proportionally with urban infrastructure density and access point concentration. Despite the presence of congested deployments, most detected access points were categorized as LOW or MEDIUM congestion, suggesting severe spectrum saturation was localized rather than uniformly distributed.

Channel congestion by city (download)

A thorough analysis of individual channel utilization revealed that channels 11, 6 and 1 consistently experienced the highest congestion levels across the three cities, which correlates with our previous findings. These channels accounted for the majority of VERY_HIGH congestion classifications, particularly within the 2.4 GHz band.

In Mexico City, channel 11 alone accounted for more than 25% of detected deployments and consistently exhibited VERY_HIGH congestion levels.

This behavior reflects the limited availability of non-overlapping channels within the 2.4 GHz spectrum and the widespread reliance on default wireless configurations.

Most congested channels by city (download)

Overall, the channel utilization analysis showed that wireless deployments are concentrated heavily within the traditional, non-overlapping 2.4 GHz channels. While this strategy reduces adjacent-channel interference, excessive access point density on the same channels can still produce significant co-channel contention and poor wireless performance in high-density urban environments.

Wireless security configurations


The next thing we evaluated was the security posture of the detected wireless networks. We analyzed the wireless security configurations advertised by access points in each of the locations.

Overall security configuration distribution


The analysis revealed that WPA2 was the dominant wireless authentication mechanism across the three cities. Mexico City had the highest WPA2 adoption rate at 81.19%, followed by Monterrey at 79.19% and Guadalajara at 77.59%.

The study found that every 6th open access point (17%) was unsafe, namely 16.5% in Mexico City, 18.5% in Guadalajara, and 17.2% in Monterrey. Open wireless deployments were consistently present across all locations, ranging between 10% and 12% of detected access points. These findings show that despite the widespread deployment of modern wireless security standards, encryption adoption remains incomplete.

Distribution of wireless authentication mechanisms across the three locations (download)

To simplify the interpretation of wireless security posture, we grouped detected networks into four categories:

  • Secure (WPA2/WPA3)
  • Insecure (Open/WEP)
  • Weak (WPA)
  • Unknown

Across the three locations, secure networks comprised most of detected deployments, accounting for approximately 82% of all access points. However, insecure open networks still account for between 10% and 12% of detected wireless infrastructure, consistent with our previous findings. It is important to mention that networks within the unknown category are not considered secure.

Mexico City had the highest percentage of secure deployments at 83.54%, while Guadalajara had the highest percentage of insecure open networks at 12.46%. Although Monterrey had the lowest percentage of insecure networks, open deployments still accounted for more than 10% of the detected access points.

Wireless security posture grouping across the three locations (download)

Although modern WPA2/WPA3 encryption standards dominate current wireless deployments, the continued presence of open and legacy WPA deployments indicates that insecure wireless configurations remain relevant from an operational standpoint. These networks may expose users to passive traffic interception, unauthorized monitoring, rogue access point attacks, and credential harvesting techniques.

WPS-enabled networks


We also analyzed Wi-Fi Protected Setup (WPS) in all the locations to evaluate additional attack surfaces. WPS is a standard feature on wireless routers that enables devices such as printers, repeaters or mobile phones to connect to a secure Wi-Fi network without manually entering a long password, typically through a PIN-based enrolled mechanism. Although WPA2 and WPA3 provide strong encryption mechanisms, the presence of WPS can introduce security weaknesses due to inherently vulnerable PIN-based enrollment methods.

By combining detections from the three locations, we found that 55% of all detected access points did not advertise WPS capabilities, leaving 45% of deployments vulnerable to WPS-based abuse. These results suggest that, despite the adoption of modern encryption standards, a significant portion of wireless infrastructure continues to expose legacy convenience features.

During the analysis, we found that Mexico City had the highest proportion of WPS-enabled networks, with 46.61% of the detected access points advertising WPS capabilities. Guadalajara was second with 43.45%, while Monterrey had the lowest proportion at 40.93%.

The percentage of detected access points advertising WPS capabilities across the three locations (download)

Almost half of the detected wireless networks in each city continued to advertise WPS, indicating that WPS prevalence is consistently high across the three cities.

Secure networks with WPS enabled


In many cases, networks classified as secure because of WPA2/WPA3 encryption still had WPS functionality enabled, which effectively increased the available attack surface.

To further assess the relationship between encryption strength and WPS exposure, we conducted a secondary analysis of secure networks (WPA2/WPA3) only. The results showed that around half of all secure deployments still exposed WPS, with the following breakdown for each city:

  • Mexico City: 53.7%
  • Guadalajara: 50.9%
  • Monterrey: 47.5%


The proportion of secure networks with WPS enabled across the three locations (download)

These findings indicate that encryption strength alone is not enough to evaluate wireless security posture because additional protocol features, such as WPS, may still expose exploitable attack vectors.

Additional security considerations


Overall, travelers operating within dense public environments are exposed not only to insecure wireless infrastructure but also to various risks associated with digital interactions. These risks include many threats, from public USB charging systems and phishing QR codes to proximity-based protocols and exposure to shared public devices, such as interactive totems or kiosks. One particular point that should be taken into account in light of our research is the issue of rogue wireless deployments.

Rogue access points are not necessarily malicious; they may be set up accidentally by misconfiguring router settings. An entry point for potential compromise might be caused by various misconfigurations, from a weak password to an insecure protocol. However, attackers deploy such unauthorized hotspots with malicious intent to infiltrate a network. Threat actors may deploy rogue access points posing as legitimate public wireless networks in airports, hotels, cafés and tourist areas. These deployments are called “evil twins” and can trick users into connecting to attacker-controlled infrastructure capable of intercepting traffic, harvesting credentials, or performing man-in-the-middle attacks. Further risk lies in the potential compromise of local network devices or even malware distribution. Such threats complement our findings, underscoring the importance of implementing traffic encryption, using a security solution and exercising extreme caution while browsing via public networks.

Conclusion


The wardriving assessment conducted in Mexico City, Guadalajara, and Monterrey revealed that modern wireless infrastructure continues to present multiple forms of operational exposure despite the widespread adoption of WPA2 and WPA3 security standards. The analysis demonstrated that wireless environments are highly standardized in all the locations, with recurring ISP deployments, default SSID naming conventions, homogeneous manufacturer distribution, and predictable channel allocation practices observed in all three cities.

Although most of the detected networks were classified as secure under WPA2/WPA3 authentication mechanisms, a significant proportion were exposing additional attack surfaces through enabled WPS functionality, default configurations, sequential SSID structures, and infrastructure metadata disclosure. This demonstrates that encryption strength alone is insufficient for evaluating the overall security posture of wireless infrastructure. Additionally, the prevalence of open networks and legacy wireless configurations indicates that insecure deployments are still operationally relevant in all the locations.

The results also showed that wireless infrastructure is heavily concentrated within the 2.4 GHz spectrum, particularly around channels 11, 6, and 1. This leads to elevated congestion and increased co-channel interference in densely populated urban environments.

SSID analysis further revealed that publicly broadcast wireless identifiers frequently expose valuable operational information about ISPs, equipment manufacturers, deployment templates, organizational ownership, and user-defined naming practices. The identification of default ISP naming conventions, sequential SSID structures, and BSSID-derived SSIDs demonstrated that many deployments prioritize operational convenience and simplicity over exposure minimization and privacy.

The scope of the threats stemming from vulnerable wireless configurations poses serious digital exposure risks for users. The widespread presence of standard deployments, predictable SSID naming and publicly exposed infrastructure identifiers can facilitate passive reconnaissance, infrastructure fingerprinting and opportunistic targeting.

Recommendations


To minimize the risks of wireless-based exposure and the attack surface related to hotspot infrastructure, we recommend taking the following measures:

  • Disable WPS functionality on wireless routers whenever possible, particularly within WPA2/WPA3 deployments.
  • Avoid using default SSID naming conventions that disclose ISP providers, router manufacturers, or deployment templates.
  • Refrain from using personal, organizational, or location-based identifiers in wireless network names.
  • Avoid configuring SSID using BSSID or naming conventions derived from MAC addresses, as these may expose hardware fingerprinting information.
  • Promote migration toward modern WPA3-capable infrastructure while removing legacy wireless protocols when operationally feasible.
  • Reduce wireless congestion by optimizing channel allocation strategies and minimizing excessive dependence on the 2.4 GHz spectrum.
  • Encourage adoption of 5 GHz and newer wireless technologies to reduce interference and improve spectrum efficiency.

The findings presented in this assessment emphasize the importance of combining strong wireless encryption standards, secure deployment practices, exposure minimization strategies, and user awareness to enhance the overall security posture of wireless environments.


securelist.com/wardriving-asse…

Cybersecurity & cyberwarfare ha ricondiviso questo.

The media in this post is not displayed to visitors. To view it, please go to the original post.

Attackers Exploit Docker and Kubernetes Misconfigurations to Escape Containers and Seize Host Control
#CyberSecurity
securebulletin.com/attackers-e…