Aggregazione volume 2 -

Officine bellotti - Via antonio gaggini 31 palermo
(venerdì, 13 marzo 16:00)

Meet’N Beat - Aggregazione Volume 2 -

una due giorni dove arte, musica, incontri fanno da collante alla cura collettiva che ricerchiamo costantemente.

VENERDÌ' 13 MARZO & SABATO 14 MARZO Officine Bellotti via A. Gagini 31 - Palermo

dalle 16 fino mezzanotte

Programma & Time table :

Venerdí 13 marzo

H/16:00

MOSTRA-ARCHIVIO COLLETTIVA

H/17:00

PRESENTAZIONE PROGETTO "AGGREGAZIONE"

H/18:00

"COME STIAMO?"

SOCIAL LAB MULTIDISCIPLINARE

• TALKS
• OPEN MIC
• ATTIVITÀ DI SCRITTURA E ASCOLTO

H/19:00

ELECTRONIC JAM, DJ SET, LIVE SET E VINYL SET W/ Powered by :

• ENIGMA SOUNDSYSTEM
• SUBTERRANEA SOUNDSYSTEM
• BALACLAVA SOUNDSYSTEM

Sabato 14 Marzo

H/18:00

"ULTIMATE KING MUSTER PALERMO"

FREESTYLE CONTEST.

SHOWCASE w/

• PICCIOTTO
• ROBSON DE ALMEIDA

LIVE SET

🔥KAOS ONE & DJ CRAIM IIII SCHELETRI TOUR

RISPETTA TE CHI TI STA INTORNO ES IL POSTO CHE CI OSPITA

scruscio.org/event/aggregazion…

SCIOPERO ANTAGONISTA PERMANENTE

online - https://RADIOSONAR.NET
(sabato, 7 marzo 11:00)

Due compa di Corpi e Terra dialogano

sulla manifesta per uno sciopero antagonista permanente

sulla sanzione fucsia lanciate dall'assemblea per il 2026.

Alle 11 su radiosonar.net

Il testo della manifesta a questo assembleacorpieterra.net/2026/…

Sanzione fucsia assembleacorpieterra.net/sanzi…

roma.convoca.la/event/sciopero…

Ciclo Corsi in Certosa

Giardino Ciro Principessa - Largo dei Savorgnan
(domenica, 8 marzo 13:30)

🗓️Quarta lezione ore 13.30
❣️ Giardino Ciro Principessa
Largo dei Savorgnan

Dopo l'ultima lezione del ciclo corso per chi vuole si parte insieme verso il corteo ⚙️👣
Si farà una pasta veloce e si va 🍝👣
🪧Corteo ore 17:00 partenza circo Massimo

roma.convoca.la/event/ciclo-co…

PRESIDIO CHE RESISTE - 6 MARZO

Parco Mitilini Stefanini Moneta - Parco Mitilini Stefanini Moneta
(venerdì, 6 marzo 13:00)

🟢Venerdì 6 🟢

-13:00 pranzo resistente

-passeggiata no al referendum no alla guerra

-18:00 iftar collettivo

-20:00 orchestra popolare spontanea

balotta.org/event/presidio-che…

PANE E FERMENTI | Primo incontro del Cerchio

Camere d'Aria - Via Guelfa 40/4
(sabato, 7 marzo 10:00)

PANE E FERMENTI | Primo incontro del Cerchio

Prima giornata aperta per imparare, praticare e condividere saperi su panificazioni e fermentazioni.

Vi aspettiamo dalla mattina per l’impasto, e/o dal pomeriggio per l’infornata.

📆 SABATO 7 MARZO

🕑 ORE 10.00 appuntamento
🕑 ORE 11.00 impasto
🕑 ORE 13.00 pranzo collettivo e suonata
🕑 ORE 17.00 infornata
🕑 ORE 19.30 cena e spettacolo

📍Camere d’Aria, via Guelfa 40/4

Prossimi incontri da concordare insieme 😀

📞Per info: Cippi 3665401342

balotta.org/event/pane-e-ferme…

There was a time when Linux was much simpler. You’d load a driver, it would find your device at boot up, or it wouldn’t. That was it. Now, though, people plug and unplug USB devices all the time and expect the system to react appropriately. [Arcanenibble] explains all “the gory details” about what really happens when you plug or unplug a device.

You might think, “Oh, libusb handles that.” But, of course, it doesn’t do the actual work. In fact, there are two possible backends: netlink or udev. However, the libusb developers strongly recommend udev. Turns out, udev also depends on netlink underneath, so if you use udev, you are sort of using netlink anyway.

If netlink sounds familiar, it is a generic BSD-socket-like API the kernel can use to send notifications to userspace. The post shows example code for listening to kernel event messages via netlink, just like udev does.

When udev sees a device add message from netlink, it resends a related udev message using… netlink! Turns out, netlink can send messages between two userspace programs, not just between the kernel and userspace. That means that the code to read udev events isn’t much different from the netlink example.

The next hoop is the udev event format. It uses a version number, but it seems stable at version 0xfeedcafe. Part of the structure contains a hash code that allows a bloom filter to quickly weed out uninteresting events, at least most of the time.

The post documents much of the obscure inner workings of USB hotplug events. However, there are some security nuances that aren’t clear. If you can explain them, we bet [Arcanenibble] would like to hear from you.

If you like digging into the Linux kernel and its friends, you might want to try creating kernel modules. If you get overwhelmed trying to read the kernel source, maybe go back a few versions.

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

The following was submitted by a Pirate supporter using the pseudonym “Hoodlump”, advocating for and sharing money advice on how to move away from the banking system towards credit unions. This article is apart of the project “Message in a Bottle”, allowing supporters of the US Pirate Party to submit editorial articles to the United States Pirate Party website.

Remember when the legendary redditor “DeepF****ingValue” ignited the hilarious short squeeze against giant hedge funds in 2021, essentially teaching the masses that it is in fact possible to shake the ground under the financial vultures that we once thought were untouchable?

It seemed like everyone went from not giving those giant hedge funds much thought to suddenly and collectively becoming aware of sinister financial practices that were always present.

Many learned what hedge funds were, what short-selling is, who the stock exchange is really for (when RobinHood banned further purchases of the GME stock) and, most importantly, that collective action seriously makes waves.

Perhaps the most important takeaway is that the correct action in our time is going to be a financial one.

After all, to whom do each and every one of us, regardless of who we are in the workforce, must answer to? Who sits at the top of the chain of command?

Ultimately, it is the shareholder; the enemy to all humankind itself.

It took for me to land a job within a financial brokerage firm to learn one important thing about banks:

They have an alternative.

While banks exist as a for-profit enterprise, using the money we all deposit as their own investment capital so that the returns can be dispersed among the vultures that already own everything, credit unions are not-for-profit.

They work the way banks are intended: for community.

The “shareholder” is you.

Instead of investing your money in weapons, tobacco, private-owned housing, etc., the credit union is allowed to invest only in the ventures that another member takes up.

According to the Credit Union National Association, credit union members save an average of $179 per member (or $376 per household) annually simply by banking with a not-for-profit cooperative rather than a shareholder-owned bank.

[1] In addition to the moral imperative, banking with a credit union actually offers better financial incentives.

(Of course it does, right? When you remove the greedy shareholder, the money suddenly becomes available to you.)

CUs offer lower fees, better savings account rates (if you don’t already know, please learn about certificates of deposit), and better loan rates.

If you want to start a business, the CU will give you personal support, as they are more directly concerned with your success, as you are not an inconsequential borrower.

When I learned about this, I immediately made the switch. I want to tell everyone and their mother and father to do the same.

Actually, I want to scream it until everyone falls in line.

We should not leave one nickel in excess to be invested by the companies that are ruining our lives and our planet.

If you have a 401k, it is a bit harder to tackle but you should absolutely still take ownership there as well.

One day, I took a look at mine and saw it was absolutely littered with weapons manufacturers, big pharma and big tech companies, and while that’s not surprising, we should not accept that either.

Your 401k likely looks the same, and if you don’t have it in you to research 100 different companies to do an ethics check and reallocate your retirement funds, don’t be shy about getting someone on the phone to help you.

You don’t need your money to be sitting in the top 500 American Companies’ hands for your golden years to be secure.

There are generally other options, and if for you there are none, perhaps you can cease any further deposits from your checks and look for better ways to invest your money yourself.

We don’t need to be relying on this broken system anymore to take care of us, because it’s clear it isn’t even trying to take care of us.

In an endless mission to put individuals before institutions, it’s important to teach said individuals how to put themselves first. This is one way you can do that.

The onus has been on us a long time now. It’s time to stop being dismissive or careless about our money, and instead be skeptical, accountable, and as the jits say, standing on business.

Sources:

[1] Credit Human

uspirates.org/message-in-a-bot…

Il 7 marzo a Prato si ricordano gli scioperi del 1944 e la deportazione di 133 lavoratori pratesi nei campi di concentramento nazisti, con la collaborazione dei fascisti locali. Uomini arrestati per aver scioperato, caricati sui treni e scomparsi dalle loro case e dalle loro fabbriche.

Organizzare proprio in quella data una manifestazione nazionale sulla cosiddetta “remigrazione”, promossa da CasaPound e dalla Rete dei Patrioti, con il coinvolgimento di esponenti politici locali, non è una scelta neutra. È una decisione politica che ignora deliberatamente il significato storico di quella giornata per la città.

La “remigrazione” non è un semplice slogan sull’immigrazione: è un concetto elaborato dall’estrema destra europea che propone rimpatri forzati e criteri di esclusione basati su origine e identità. Un’impostazione incompatibile con i principi costituzionali e con la storia democratica di Prato.

Si può discutere di lavoro, sicurezza e legalità. Ma scegliere il 7 marzo significa collocare quel dibattito nel giorno in cui questa città ricorda persone portate via in nome dell’ordine e dell’autorità.

Il silenzio, di fronte a una scelta del genere, non è neutralità.

La memoria non è un dettaglio formale. È un limite politico e morale.

PER QUESTO SABATO 7 MARZO ALLE ORE 16:00 POSSIBILE SARÀ IN PIAZZA DELLE CARCERI, A PRATO, ALLA MANIFESTAZIONE CONTRO LE DEPORTAZIONI “MAI PIÙ FASCISMI. MAI PIÙ DEPORTAZIONI.”

Possibile Prato-Pistoia

L'articolo 7 marzo: saremo in piazza a Prato contro la manifestazione di CasaPound sulla “remigrazione” proviene da Possibile.

The fourth quarter of 2025 went down as one of the most intense periods on record for high-profile, critical vulnerability disclosures, hitting popular libraries and mainstream applications. Several of these vulnerabilities were picked up by attackers and exploited in the wild almost immediately.

In this report, we dive into the statistics on published vulnerabilities and exploits, as well as the known vulnerabilities leveraged with popular C2 frameworks throughout Q4 2025.

Statistics on registered vulnerabilities

This section contains statistics on registered vulnerabilities. The data is taken from cve.org.

Let’s take a look at the number of registered CVEs for each month over the last five years, up to and including the end of 2025. As predicted in our last report, Q4 saw a higher number of registered vulnerabilities than the same period in 2024, and the year-end totals also cleared the bar set the previous year.

Total published vulnerabilities by month from 2021 through 2025 (download)

Now, let’s look at the number of new critical vulnerabilities (CVSS > 8.9) for that same period.

Total number of published critical vulnerabilities by month from 2021 to 2025< (download)

The graph shows that the volume of critical vulnerabilities remains quite substantial; however, in the second half of the year, we saw those numbers dip back down to levels seen in 2023. This was due to vulnerability churn: a handful of published security issues were revoked. The widespread adoption of secure development practices and the move toward safer languages also pushed those numbers down, though even that couldn’t stop the overall flood of vulnerabilities.

Exploitation statistics

This section contains statistics on the use of exploits in Q4 2025. The data is based on open sources and our telemetry.

Windows and Linux vulnerability exploitation

In Q4 2025, the most prevalent exploits targeted the exact same vulnerabilities that dominated the threat landscape throughout the rest of the year. These were exploits targeting Microsoft Office products with unpatched security flaws.

Kaspersky solutions detected the most exploits on the Windows platform for the following vulnerabilities:

• CVE-2018-0802: a remote code execution vulnerability in Equation Editor.
• CVE-2017-11882: another remote code execution vulnerability, also affecting Equation Editor.
• CVE-2017-0199: a vulnerability in Microsoft Office and WordPad that allows an attacker to assume control of the system.

The list has remained unchanged for years.

We also see that attackers continue to adapt exploits for directory traversal vulnerabilities (CWE-35) when unpacking archives in WinRAR. They are being heavily leveraged to gain initial access via malicious archives on the Windows operating system:

• CVE-2023-38831: a vulnerability stemming from the improper handling of objects within an archive.
• CVE-2025-6218 (formerly ZDI-CAN-27198): a vulnerability that enables an attacker to specify a relative path and extract files into an arbitrary directory. This can lead to arbitrary code execution. We covered this vulnerability in detail in our Q2 2025 report.
• CVE-2025-8088: a vulnerability we analyzed in our previous report, analogous to CVE-2025-6218. The attackers used NTFS streams to circumvent controls on the directory into which files were being unpacked.

As in the previous quarter, we see a rise in the use of archiver exploits, with fresh vulnerabilities increasingly appearing in attacks.

Below are the exploit detection trends for Windows users over the last two years.

Dynamics of the number of Windows users encountering exploits, Q1 2024 – Q4 2025. The number of users who encountered exploits in Q1 2024 is taken as 100% (download)

The vulnerabilities listed here can be used to gain initial access to a vulnerable system. This highlights the critical importance of timely security updates for all affected software.

On Linux-based devices, the most frequently detected exploits targeted the following vulnerabilities:

• CVE-2022-0847, also known as Dirty Pipe: a vulnerability that allows privilege escalation and enables attackers to take control of running applications.
• CVE-2019-13272: a vulnerability caused by improper handling of privilege inheritance, which can be exploited to achieve privilege escalation.
• CVE-2021-22555: a heap overflow vulnerability in the Netfilter kernel subsystem.
• CVE-2023-32233: another vulnerability in the Netfilter subsystem that creates a use-after-free condition, allowing for privilege escalation due to the improper handling of network requests.

Dynamics of the number of Linux users encountering exploits, Q1 2024 – Q4 2025. The number of users who encountered exploits in Q1 2024 is taken as 100% (download)

We are seeing a massive surge in Linux-based exploit attempts: in Q4, the number of affected users doubled compared to Q3. Our statistics show that the final quarter of the year accounted for more than half of all Linux exploit attacks recorded for the entire year. This surge is primarily driven by the rapidly growing number of Linux-based consumer devices. This trend naturally attracts the attention of threat actors, making the installation of security patches critically important.

Most common published exploits

The distribution of published exploits by software type in Q4 2025 largely mirrors the patterns observed in the previous quarter. The majority of exploits we investigate through our monitoring of public research, news, and PoCs continue to target vulnerabilities within operating systems.

Distribution of published exploits by platform, Q1 2025 (download)

Distribution of published exploits by platform, Q2 2025 (download)

Distribution of published exploits by platform, Q3 2025 (download)

Distribution of published exploits by platform, Q4 2025 (download)

In Q4 2025, no public exploits for Microsoft Office products emerged; the bulk of the vulnerabilities were issues discovered in system components. When calculating our statistics, we placed these in the OS category.

Vulnerability exploitation in APT attacks

We analyzed which vulnerabilities were utilized in APT attacks during Q4 2025. The following rankings draw on our telemetry, research, and open-source data.

TOP 10 vulnerabilities exploited in APT attacks, Q4 2025 (download)

In Q4 2025, APT attacks most frequently exploited fresh vulnerabilities published within the last six months. We believe that these CVEs will remain favorites among attackers for a long time, as fixing them may require significant structural changes to the vulnerable applications or the user’s system. Often, replacing or updating the affected components requires a significant amount of resources. Consequently, the probability of an attack through such vulnerabilities may persist. Some of these new vulnerabilities are likely to become frequent tools for lateral movement within user infrastructure, as the corresponding security flaws have been discovered in network services that are accessible without authentication. This heavy exploitation of very recently registered vulnerabilities highlights the ability of threat actors to rapidly implement new techniques and adapt old ones for their attacks. Therefore, we strongly recommend applying the security patches provided by vendors.

C2 frameworks

In this section, we will look at the most popular C2 frameworks used by threat actors and analyze the vulnerabilities whose exploits interacted with C2 agents in APT attacks.

The chart below shows the frequency of known C2 framework usage in attacks against users during Q4 2025, according to open sources.

TOP 10 C2 frameworks used by APTs to compromise user systems in Q4 2025 (download)

Despite the significant footprints it can leave when used in its default configuration, Sliver continues to hold the top spot among the most common C2 frameworks in our Q4 2025 analysis. Mythic and Havoc were second and third, respectively. After reviewing open sources and analyzing malicious C2 agent samples that contained exploits, we found that the following vulnerabilities were used in APT attacks involving the C2 frameworks mentioned above:

• CVE-2025-55182: a React2Shell vulnerability in React Server Components that allows an unauthenticated user to send commands directly to the server and execute them from RAM.
• CVE-2023-36884: a vulnerability in the Windows Search component that allows the execution of commands on a system, bypassing security mechanisms built into Microsoft Office applications.
• CVE-2025-53770: a critical insecure deserialization vulnerability in Microsoft SharePoint that allows an unauthenticated user to execute commands on the server.
• CVE-2020-1472, also known as Zerologon, allows for compromising a vulnerable domain controller and executing commands as a privileged user.
• CVE-2021-34527, also known as PrintNightmare, exploits flaws in the Windows print spooler subsystem, enabling remote access to a vulnerable OS and high-privilege command execution.
• CVE-2025-8088 and CVE-2025-6218 are similar directory-traversal vulnerabilities that allow extracting files from an archive to a predefined path without the archiving utility notifying the user.

The set of vulnerabilities described above suggests that attackers have been using them for initial access and early-stage maneuvers in vulnerable systems to create a springboard for deploying a C2 agent. The list of vulnerabilities includes both zero-days and well-known, established security issues.

Notable vulnerabilities

This section highlights the most noteworthy vulnerabilities that were publicly disclosed in Q4 2025 and have a publicly available description.

React2Shell (CVE-2025-55182): a vulnerability in React Server Components

We typically describe vulnerabilities affecting a specific application. CVE-2025-55182 stood out as an exception, as it was discovered in React, a library primarily used for building web applications. This means that exploiting the vulnerability could potentially disrupt a vast number of applications that rely on the library. The vulnerability itself lies in the interaction mechanism between the client and server components, which is built on sending serialized objects. If an attacker sends serialized data containing malicious functionality, they can execute JavaScript commands directly on the server, bypassing all client-side request validation. Technical details about this vulnerability and an example of how Kaspersky solutions detect it can be found in our article.

CVE-2025-54100: command injection during the execution of curl (Invoke-WebRequest)

This vulnerability represents a data-handling flaw that occurs when retrieving information from a remote server: when executing the curl or Invoke-WebRequest command, Windows launches Internet Explorer in the background. This can lead to a cross-site scripting (XSS) attack.

CVE-2025-11001: a vulnerability in 7-Zip

This vulnerability reinforces the trend of exploiting security flaws found in file archivers. The core of CVE-2025-11001 lies in the incorrect handling of symbolic links. An attacker can craft an archive so that when it is extracted into an arbitrary directory, its contents end up in the location pointed to by a symbolic link. The likelihood of exploiting this vulnerability is significantly reduced because utilizing such functionality requires the user opening the archive to possess system administrator privileges.

This vulnerability was associated with a wave of misleading news reports claiming it was being used in real-world attacks against end users. This misconception stemmed from an error in the security bulletin.

RediShell (CVE-2025-49844): a vulnerability in Redis

The year 2025 saw a surge in high-profile vulnerabilities, several of which were significant enough to earn a unique nickname. This was the case with CVE-2025-49844, also known as RediShell, which was unveiled during a hacking competition. This vulnerability is a use-after-free issue related to how the load command functions within Lua interpreter scripts. To execute the attack, an attacker needs to prepare a malicious script and load it into the interpreter.

As with any named vulnerability, RediShell was immediately weaponized by threat actors and spammers, albeit in a somewhat unconventional manner. Because technical details were initially scarce following its disclosure, the internet was flooded with fake PoC exploits and scanners claiming to test for the vulnerability. In the best-case scenario, these tools were non-functional; in the worst, they infected the system. Notably, these fraudulent projects were frequently generated using LLMs. They followed a standardized template and often cross-referenced source code from other identical fake repositories.

CVE-2025-24990: a vulnerability in the ltmdm64.sys driver

Driver vulnerabilities are often discovered in legitimate third-party applications that have been part of the official OS distribution for a long time. Thus, CVE-2025-24990 has existed within code shipped by Microsoft throughout nearly the entire history of Windows. The vulnerable driver has been shipped since at least Windows 7 as a third-party driver for Agere Modem. According to Microsoft, this driver is no longer supported and, following the discovery of the flaw, was removed from the OS distribution entirely.

The vulnerability itself is straightforward: insecure handling of IOCTL codes leading to a null pointer dereference. Successful exploitation can lead to arbitrary command execution or a system crash resulting in a blue screen of death (BSOD) on modern systems.

CVE-2025-59287: a vulnerability in Windows Server Update Services (WSUS)

CVE-2025-59287 represents a textbook case of insecure deserialization. Exploitation is possible without any form of authentication; due to its ease of use, this vulnerability rapidly gained traction among threat actors. Technical details and detection methodologies for our product suite have been covered in our previous advisories.

Conclusion and advice

In Q4 2025, the rate of vulnerability registration has shown no signs of slowing down. Consequently, consistent monitoring and the timely application of security patches have become more critical than ever. To ensure resilient defense, it is vital to regularly assess and remediate known vulnerabilities while implementing technology designed to mitigate the impact of potential exploits.

Continuous monitoring of infrastructure, including the network perimeter, allows for the timely identification of threats and prevents them from escalating. Effective security also demands tracking the current threat landscape and applying preventative measures to minimize risks associated with system flaws. Kaspersky Next serves as a reliable partner in this process, providing real-time identification and detailed mapping of vulnerabilities within the environment.

Securing the workplace remains a top priority. Protecting corporate devices requires the adoption of solutions capable of blocking malware and preventing it from spreading. Beyond basic measures, organizations should implement adaptive systems that allow for the rapid deployment of security updates and the automation of patch management workflows.

securelist.com/vulnerabilities…

Light aircraft often use a heading indicator as a way to know where they’re going. Retired instrumentation engineer [Don Welch] recreated a heading indicator of his own, using cheap off-the-shelf hardware to get the job done.

The heart of the build is a Teensy 4.0 microcontroller. It’s paired with a BNO085 inertial measurement unit (IMU), which combines a 3-axis gyro, 3-axis accelerometer, and 3-axis magnetometer into a single package. [Don] wanted to build a heading indicator that was immune to magnetic disturbances, so ignored the magnetometer readings entirely, using the rest of the IMU data instead.

Upon startup, the Teensy 4.0 initializes a small round TFT display, and draws the usual compass rose with North at the top of the display. Any motion after this will update the heading display accordingly, with [Don] noting the IMU has a fast update rate of 200 Hz for excellent motion tracking. The device does not self-calibrate to magnetic North; instead, an encoder can be used to calibrate the device to match a magnetic compass you have on hand. Or, you can just ensure it’s already facing North when you turn it on.

Thanks to the power of the Teensy 4.0 and the rapid updates of the BNO085, the display updates are nicely smooth and responsive. However, [Don] notes that it’s probably not quite an aircraft-spec build. We’ve featured some interesting investigations of just how much you can expect out of MEMS-based sensors like these before, too.

youtube.com/embed/UoS7PKGJVlE?…

hackaday.com/2026/03/06/buildi…

Electric vehicles are everywhere these days, and with them comes along a whole slew of charging infrastructure. The fastest of these are high-power machines that can deliver enough energy to charge a car in well under an hour, but there are plenty of slower chargers available that take much longer. These don’t tend to require any specialized equipment which makes them easier to install in homes and other places where there isn’t as much power available. In fact, these chargers generally amount to fancy extension cords, and [Matt Gray] realized he could use these to do other things like charge his electric bicycle.

To begin the build, [Matt] started with an electric car charging socket and designed a housing for it with CAD software. The housing also holds the actual battery charger for his VanMoof bicycle, connected internally directly to the car charging socket. These lower powered chargers don’t require any communication from the vehicle either, which simplifies the process considerably. They do still need to be turned on via a smartphone app so the energy can be metered and billed, but with all that out of the way [Matt] was able to take his test rig out to a lamppost charger and boil a kettle of water.

After the kettle experiment, he worked on miniaturizing his project so it fits more conveniently inside the 3D-printed enclosure on the rear rack of his bicycle. The only real inconvenience of this project, though, is that since these chargers are meant for passenger vehicles they’re a bit bulky for smaller vehicles like e-bikes. But this will greatly expand [Matt]’s ability to use his ebike for longer trips, and car charging infrastructure like this has started being used in all kinds of other novel ways as well.

youtube.com/embed/i6IyukCIia8?…

hackaday.com/2026/03/05/ebike-…