Cisco ha espresso preoccupazione per la bozza della convenzione internazionale sulla criminalità informatica delle Nazioni Unite, affermando che il documento deve essere migliorato prima di essere messo ai voti.

Il Trattato Globale sulla criminalità informatica è stato proposto dalla Russia nel 2017, il suo obiettivo principale è quello di sviluppare standard globali relativi al problema dei crimini informatici transnazionali.

Da quando sono iniziati i lavori sul trattato nel 2019, la comunità internazionale non ha raggiunto un consenso sulle sue necessità e sui suoi obiettivi. Nonostante tutti i dubbi, l’accordo è stato adottato dopo 3 anni di negoziati, conclusisi con una sessione di due settimane.

Tuttavia, organizzazioni per i diritti umani come Human Rights Watch (HRW) e Electronic Frontier Foundation ( EFF ) hanno criticato il Trattato per essere eccessivamente ampio nel linguaggio e potrebbe essere utilizzato per perseguitare i cittadini che esprimono opinioni discutibili.

Preoccupante è anche la clausola sulla privacy, che consente agli Stati di richiedere dati ai fornitori senza informare i cittadini.

Anche l’organizzazione britannica per i diritti umani Article 19 teme che un linguaggio così vago possa ostacolare la ricerca legittima sulla sicurezza informatica, poiché i professionisti potrebbero temere di essere perseguiti.

Eric Wenger, direttore senior delle politiche tecnologiche di Cisco, ha fatto eco a queste preoccupazioni, affermando che la convenzione, piuttosto che concentrarsi su specifici crimini informatici, mira a frenare in modo più ampio l’uso delle reti di computer per diffondere informazioni indesiderate. Secondo Wenger ciò è contrario ai principi della libertà di parola e richiede modifiche.

Cisco non è contraria alla creazione di una convenzione internazionale sulla criminalità informatica, ma ritiene che dovrebbe proteggere i diritti umani e lo stato di diritto. Nella sua forma attuale, il documento, secondo la società, non fornisce una tutela sufficiente a tali principi.

L'articolo Cisco Contraria alla Convenzione Internazionale sul Cybercrime dell’ONU proviene da il blog della sicurezza informatica.

It might seem like the days of MS-DOS were a lifetime ago because…well, they basically were. Version 6.22 of the venerable operating system, the last standalone release, came out back in 1994. That makes even the most recent version officially 30 years old. A lot has changed in the computing world since that time, so naturally trying to run such an ancient OS on even a half-way modern machine would be a waste of time. Right?

As it turns out, getting MS-DOS 6.22 running on a modern computer isn’t nearly as hard as you’d think. In fact, it works pretty much perfectly. Assuming, that is, you pick the right machine. [Yeo Kheng Meng] recently wrote in to share his experiments with running the final DOS release on his Intel-powered ThinkPad X13 from 2020, and the results are surprising to say the least.

To be clear, we’re not talking about some patched version of DOS here. There’s no emulator at work either. Granted [Yeo] did embrace a few modern conveniences, such as using a USB floppy drive emulator to load the disk images instead of fiddling with actual floppies, and installing DOS onto an external drive so as not to clobber his actual OS on the internal NVME drive. But other than that, the installation of DOS on the ThinkPad went along just as it would have in the 1990s.

IBM’s 1984 luggable running the same OS as a modern ThinkPad
It’s impressive enough that MS-DOS can still be installed on such a modern machine. But what’s really surprising is how well it all works. [Yeo] reports that the bulk of the ThinkPad’s hardware worked as expected, although he did have to pull in some modern open source drivers such as SBEMU, which makes DOS think the laptop’s Intel HD audio chip is an old school Sound Blaster card. He was even able to get several different Thunderbolt-connected Gigabit Ethernet adapters working.

Not all of the DOS benchmark tools [Yeo] tried on the machine would actually run, but as you might imagine, the ones that did reported some fairly spectacular results. After all, a machine with specs like this would have been the stuff of science fiction when those tools were written.

So how is this all possible? [Yeo] notes that this is one of the final Lenovo laptops to support “Legacy BIOS” mode, as everything after this point is pure UEFI. This particular machine also features a “Thunderbolt BIOS Assist Mode” which makes connected devices seem like standard PCI cards.

In the end, the experiment shows that Intel and Lenovo have done an incredible job of maintaining backwards compatibility with their respective hardware. While it seems like this is the end of the road for your average consumer computer due to issues such as the UEFI switch over, don’t worry. You’ll still be able to scratch that retro itch with the right hardware.

youtube.com/embed/-mTmZqoNeFA?…

Gli ingegneri dell’azienda cinese Alibaba hanno presentato un nuovo modello di apprendimento automatico multimodale chiamato mPLUG-Owl3. Questo modello è in grado di analizzare in modo efficiente testo, immagini e video.

Gli sviluppatori prestano particolare attenzione alla velocità della rete neurale, sostenendo che bastano solo quattro secondi per elaborare un video di due ore.

mPLUG-Owl3 si basa sul modello Qwen2, che è stato notevolmente migliorato e ottimizzato. Grazie a queste modifiche, il tempo di attesa per il primo token è stato ridotto di sei volte e una singola scheda grafica A100 ora può elaborare fino a 400 immagini al secondo.

Il modello utilizza anche uno speciale blocco HATB (Hyper Attention Transformer), che integra funzionalità visive e testuali, consentendo, ad esempio, di cercare immagini visive in base a query testuali.

Il codice del progetto è aperto e pubblicato su GitHub. Inoltre, gli sviluppatori hanno fornito tutto il materiale necessario per lavorare sulle piattaforme Hugging Face e sull’analogo cinese Model Scope.

Il testo completo dello studio descrive in dettaglio lo sviluppo e il funzionamento del modello mPLUG-Owl3.

L'articolo Alibaba presenta mPLUG-Owl3. Il modello che può analizzare 400 immagini al secondo su una sola A100 proviene da il blog della sicurezza informatica.

Following a major breach of the European Parliament's recruitment system in April 2024, when sensitive personal information was exposed, Nyob filed two legal complaints for alleged data protection law violations on Thursday (22 August), against the EU institute.

euractiv.com/section/cybersecu…

slowforward.net/2024/08/22/cit…

slowforward

2024-08-22 07:31:21

grazie a Gaetano Altopiano per la sempre gentilissima ospitalità sul sito da lui curato:

ilcucchiaionellorecchio.it/202…

slowforward.net/2024/08/22/cit…

#000000 #CittadinaConTorreNelNome #IlCucchiaioNellOrecchio #prosa #prosaBreve #ProsaInProsa #proseBrevi #scrittureDiRicerca #testiDiMgInRete #testiDiMgOnline

“cittadina con torre nel nome”, su ‘il cucchiaio nell’orecchio’

^slowforward

As a cybersecurity company, before we release our products, we perform penetration tests on them to make sure they are secure. Recently, new versions of KasperskyOS-based products were released, namely Kaspersky Thin Client (KTC) and Kaspersky IoT Secure Gateway (KISG). As part of the pre-release penetration testing, we analyzed two open-source components used in these products, namely Suricata and FreeRDP projects, and discovered several vulnerabilities, which we reported to the developers of the corresponding libraries, as well as sharing the fuzzing tests we used to test FreeRDP.

The community confirmed the reported issues and registered the following CVEs:

• FreeRDP: CVE-2024-32041, CVE-2024-32039, CVE-2024-32040, CVE-2024-32458, CVE-2024-32459, CVE-2024-32460
• Suricata: CVE-2024-32664

Later, using our fuzzing tests, the community found about 10 more vulnerabilities in FreeRDP. All issues were fixed in both open-source projects and in our products prior to the new version releases.

Open-source components in KasperskyOS-based products

KasperskyOS is a microkernel operating system designed to be Cyber Immune. The attack surface is minimized by the built-in security mechanisms, the small size of the microkernel and domain (component) isolation. The latter allows secure implementation of open-source components: even if a particular component contains vulnerabilities, the isolation prevents most of the damage that could be caused by their exploitation.

The KasperskyOS-based products in question are complex, support various protocols and applications and include open-source components that implement some of their functions. As its name suggests, FreeRDP is an open-source implementation of Remote Desktop Protocol. It is used in Kaspersky Thin Client, where it is responsible for remote connection capabilities.

Suricata is a network monitoring, intrusion detection and prevention system developed by the Open Information Security Foundation and the Suricata community. It is widely used and implemented by most public and private organizations. When it comes to KasperskyOS-based products, Suricata is used in KISG, where it is responsible for detecting network attacks. It receives a copy of network traffic, analyzes it according to a set of rules and issues alerts if an attack is detected.

Although component isolation in KasperskyOS ensures the security of our products even if an open-source component contains vulnerabilities, when assessing the security of our products we follow the defense-in-depth approach. The OS design minimizes the attack surface, but it can’t stop cybercriminals and high-profile actors from trying to find a way to penetrate the system. That’s why we test (and, if necessary, fix) all components of our products, including the open-source projects we use.

Penetration testing begins by describing the entire attack surface, which includes all components and all known attack vectors against them.

CVE-2024-32664: out-of-bounds write in Suricata

During our penetration testing activities we found three issues in Suricata. Two of them were considered bad practice, and one was registered as CVE-2024-32664. The vulnerability affects all Suricata versions from 6.0.0 to 6.0.18 and from 7.0.0 to 7.0.4, and is fixed in versions 6.0.19 and 7.0.5. It was initially assessed as being a medium severity issue (CVSS 5.3). However, in the tickets on the Open Information Security Foundation website, the severity was changed to high for versions 7.0.x and to critical for 6.0.x.

The vulnerability resides in Suricata’s base64 decoding function, DecodeBase64, and belongs to the out-of-bounds write type. In a situation where the buffer is full, it is possible to use specially crafted input to trick the function into thinking that there is some space left and writing three more bytes to the buffer. In base64, if the size of the unencoded data is not a multiple of three, a padding is added to the encoded output. It typically equals one or two. The decoding function accepts encoded data as input, which means that the padding is controlled by the attacker. If they provide an encoded string where the padding equals three or four, a memory corruption occurs, leading to a limited buffer overflow, which may result in remote code execution.

Vulnerable code in Suricata:
line 45 – if ‘padding’ is equal to B64_BLOCK(4) or ASCII_BLOCK(3), ‘numDecoded_blk’ will be set to 0;
line 46 – we will pass this check, as ‘dest_size’ is equal to ‘*decoded_bytes’;
line 53 – 3 bytes will be written past the end of buffer ‘dptr’;
line 72 – similar issue.

The issue was patched in Suricata versions 6.0.19 and 7.0.5. For those, who are unable to install these updates, the following recommendations to mitigate the threat were provided by the community:

• Do not load untrusted datasets
• Do not use rules with a ‘base64_decode’ keyword with a ‘bytes’ option with a value of 1, 2 or 5

For the software versions 7.0.x you can also set ‘app-layer.protocols.smtp.mime.body-md5’ to false.

FreeRDP vulnerabilities

The vulnerabilities in FreeRDP were found using a simple FreeRDP fuzzer. They affect all FreeRDP 3.x.x versions prior to 3.5.0 and all FreeRDP 2.x.x versions prior to 2.11.6, where they were fixed.

CVE-2024-32041

This vulnerability resides in the zgfx_decompress_segment function of the ZGFX decoder and is an out-of-bounds read vulnerability. The absence of a necessary check may lead to a situation where a certain number of bytes of data are accessed that shouldn’t be.

This vulnerability may be exploited by a malicious server to gain access to a portion of the client memory. It may be used to bypass address space layout randomization (ASLR) to get the address space layout for a particular process and perform an attack against that process.

Vulnerable code in the ‘zgfx_decompress_segment’ function:
line 48 – the variable ‘count’ is checked to make sure it is not greater than the size of allocated space in the output buffer;
lines 54-55 – the variable ‘count’ is not checked against the size of the decoded array. Hence the out-of-bounds read.

As a workaround for users who cannot install the fixed version of FreeRDP, the community recommends deactivating the “/gfx” connection method, which is on by default, and set “/bpp” or “/rfx” instead.

CVE-2024-32039

This is an integer overflow and out-of-bounds write vulnerability in the clear_decompress_residual_data function in the Clear codec component. The ‘runLengthFactor’ variable is read from the stream, which can be controlled by the attacker. The code performs a sanity check to make sure it is not bigger than the size of the array to be written to. This sanity check contains an error that allows the attacker to bypass it via unsigned integer overflow and write outside the allocated buffer. Exploitation of this vulnerability could lead to remote code execution on the client.

Vulnerable code in the ‘clear_decompress_residual_data’ function:
line 23 – the variable ‘runLengthFactor’ is an unsigned integer (uint32);
line 42 – the variable ‘runLengthFactor’ is read from the stream;
line 47 – due to an unsigned integer overflow, if the ‘runLengthFactor’ value is large enough, the ‘pixelIndex+runLengthFactor’ value approaches zero, and the check is passed;
lines 56-60 – the ‘for’ cycle uses the original ‘runLengthFactor’ value and is written outside ‘dstBuffer’.

As a workaround for the unpatched versions, it is recommended to use “/bpp:32” or “/rfx” instead of the “/gfx” codec that is enabled by default.

CVE-2024-32040

This integer underflow vulnerability affects FreeRDP connections that use the NSC codec responsible for bitmap compression. It resides in the nsc_rle_decode function of this component. The absence of a necessary check may lead to a situation when the size of unprocessed input data is less than 0. As it is an unsigned integer variable, it will become a large positive value in this case. This may lead to an out-of-bounds read of a large amount of data.

Vulnerable code in the nsc_rle_decode function:
lines 45-48 – the variable ‘len’ is read from the attacker-controlled stream;
line 51 – suppose ‘len’ is a large integer and it is less than ‘outSize’, thus we can pass this check;
line 57 – there is no check to ensure that ‘left’ is greater than ‘len’, which may result in an unsigned integer underflow, and the big value of the ‘left’ variable;
line 6 – the big value of the ‘left’ variable passes the check, and the next iteration starts reading outside the memory bounds.

As a workaround in a situation where installing the patched version is impossible, it is recommended not to use the codec in question.

CVE-2024-32458

This is an out-of-bounds read vulnerability in the planar_skip_plane_rle function in the Planar codec component. No checks are implemented for the planes array elements in the function code. As a result, the SrcSize variable may exceed the amount of available data, which may result in an out-of-bounds read. An attacker may attempt to bypass ASLR using this vulnerability.

Vulnerable code in the planar_skip_plane_rle function:
line 13 – no check is performed to ensure the size is no less than the offset to plane. If it is small enough, an unsigned integer underflow occurs;
line 45 – as a result, SrcSize can exceed the amount of available data;
line 52 – out-of-bounds read on this line.

You can find the fix for the vulnerability here. As a workaround for unpatched systems, it is recommended to use “/gfx” or “/rfx” connection methods. Note that the “/gfx” method is enabled by default and it is recommended to disable it to mitigate other vulnerabilities in this list.

CVE-2024-32459

This is an out-of-bounds read vulnerability in ncrush_decompress function of the ncrush codec. If the source data size is small, up to four extra bytes could be read, which could be used to bypass ASLR.

Vulnerable code in the ‘ncrush_decompress’ function:
Line 18 – Out-of-bounds read if SrcSize is less than 4.

There are no workarounds for the unpatched versions of the FreeRDP client.

CVE-2024-32460

This is an out-of-bounds read vulnerability in ExtractRunLengthLiteFgBg function in the Interleaved codec component. It affects FreeRDP clients that use the legacy “GDI” drawing path for transmitting graphics from the remote desktop. This function accepts the pointer to the first element after the allocated buffer and incorrectly handles the ‘buffer_within_range’ helper, causing it to read one byte outside the buffer.

Vulnerable code in the ExtractRunLengthLiteFgBg function:
line 11 – ‘pbEnd’ points to the first byte after the end of buffer;
line 26 – the ‘ExtractRunLength’ function is called with ‘pbEnd’ as the third parameter;
line 51 – the ‘ExtractRunLengthLiteFgBg’ function is called with ‘pbEnd’ as a second parameter;
line 77 – the ‘ExtractRunLengthLiteFgBg’ function checks that there is one byte before the end of the buffer;
line 82 – the code reads one byte outside of the allocated buffer.

You can find the fix for the vulnerability here. The workaround for unpatched systems could be to use more recent settings such as “/gfx” or “/rfx” if the server supports them. Note that some of the other vulnerabilities in this list affect FreeRDP clients that use “/gfx” as the drawing path.

We shared our fuzzing tests with the FreeRDP community, along with information about the vulnerabilities that were found. They ran them against various codecs used in the software and found 10 more vulnerabilities in the following components:

• Clear codec
• Color codec
• Interleaved codec
• NSC codec
• ZGFX codec

Most of these vulnerabilities are out-of-bounds reads that can be used to bypass the ASLR security measure. All of them were fixed in versions 3.5.1 and 2.11.7.

Disclosure timeline

• 28.03.2024 – We shared information about the vulnerabilities with the Suricata community.
• 15.04.2024 – We reported the discovered vulnerabilities to the FreeRDP community.
• 16.04.2024 – FreeRDP fixes issued.
• 20.04.2024 – Fixes issued for the vulnerabilities discovered by the community using our fuzzer.
• 23.04.2024 – Patched Suricata versions issued.

Conclusion

The concept of secure by design applies not only to system architecture, but also to the development process itself. Moreover, by testing and trying all the system components prior to release, we were able to help the community fix a range of issues in two widely used open-source projects. We would like to thank the Suricata and FreeRDP maintainers for their quick response to our reports and prompt release of the patches.

If you use this software, we encourage you to update to the latest versions as soon as possible. At the time of publication, the most up-to-date versions are:

• 6.0.20 and 7.0.6 for Suricata;
• 2.11.7 and 3.7.0 for FreeRDP.

securelist.com/suricata-freerd…

SITO PRINCIPALE:
slowforward.net = tinyurl.com/slowforward = t.ly/fsRQj

BLOG di politica e ricerca letteraria, gemello eterozigote di slowforward:
differx.noblogs.org/ = tinyurl.com/differx = t.ly/ms-9d

spazio principale per immagini e materiali vari, su tumblr:
differx.tumblr.com

diario, segnalazione di link, blog personale:
ko-fi.com/differx57119/posts = tinyurl.com/differxx = t.ly/WNEJ0

mastodon: 
mastodon.uno/@differx

friendica: 
poliverso.org/profile/differx

bluesky: 
bsky.app/profile/differx.bsky.…

instagram: 
instagram.com/marco.giovenale

slowforward.net/2024/08/21/agg…

slowforward

2024-08-21 11:35:45

ATTENZIONE, contenuti forti

qui:

e
slowforward.net/2024/08/21/uni…

slowforward.net/2024/08/21/agg…

#aggiornamenti #ff0000 #Gaza #genocide #genocidio #izrahellGenocidalState #izrahellTerroristState #massacri #Palestina #Palestine #zionism

aggiornamenti ulteriori e continui sui massacri di agosto

ATTENZIONE, contenuti forti qui: e

^slowforward

slowforward.net/2024/08/21/a-r…

slowforward

2024-08-21 10:59:35

cliccare per ingrandire

cliccare per ingrandire

PDF completo degli eventi:
Di là dal fiume 2024_/ settima edizione_/ PROGRAMMA_/ a cura di teatroinscatola

Incontri a ingresso gratuito

slowforward.net/2024/08/21/a-r…

#000000 #2024 #AEKLauchlan #AlbertoPrunetti #AlessandraVanzi #AllegraSeganti #amianto #AmiantoUnaStoriaOperaia #AriannaNinchi #AssociazioneKAlma #ASTRAL #BibliotecaElioPagliarani #CAE #CasaDelPrimoMunicipio #CasaSocialeDellePersoneAdulteDiTrastevere #CharlieChaplin #CittàDellAltraEconomia #ComuneDiAlbanoLaziale #ComuneDiRoma #CONFAEL_ #Confael #Congerie #CristinaAubry #CSVLazio #DiLavoroSiVive #DiLàDalFiume #ElioPagliarani #ElisabettaLongone #ElisabettaVillaggio #ExperimentumMundi #Fantozzi #FaròArte #ff0000 #FlaminiaCasucci #GabrielMaldonado #GalleriaArteMakita #GiorgioBattistelli #IlCantiere #inail #ITISGGalilei #JohnCage #LorenzoCiccarelli #LucaMazzara #LucianoSalce #ManuelFiorentini #MarcoGiovenale #MassimoAlessandrini #Mattatoio #MaurizioDiLoreti #Ostiense #PalazzoDellaRegioneLazio #PaoloVillaggio #PasseggiandoConSilvia #PinoBertelli #PoloMusealeDeiTrasporti #Ponte #RaccontiDiLavoro #RevolutionAnyone #RobertTressel #SalaTirreno #SebastianoDiBari #SergejĖjzenštejn #SetteStradePerSetteMestieri #Teatroinscatola #Testaccio #VIIEdizione #Ėjzenštejn

a roma, da oggi, 21 agosto, al 6 settembre: “di là dal fiume”, settima edizione – a cura di teatroinscatola

Programma completo del festival “Di là dal fiume”, VII edizione, a cura del teatroinscatola

^slowforward

slowforward.net/2024/08/21/ago…

slowforward

2024-08-21 07:31:03

Agosto

Il 29 agosto s’inaugura alle 17:00 la mostra Giuliano Scabia e Franco Basaglia in viaggio accanto alla follia: da Marco Cavallo al Drago di Montelupo presso Murate Art District (M.A.D., Piazza delle Murate).

La mostra sarà visitabile fino al 26 settembre.

Il 29 agosto alle 18:00, in occasione dell’inaugurazione, l’Accademia della Follia – Claudio Misculin metterà in scena lo spettacolo Quelli di Basaglia… A 180 gradi.

Sempre alle 18:00, il 31 agosto: Teatro al tramonto (con momento conviviale) nel campo di Paolo sulle colline di Marignolle in Via Bernardino Poccetti, 19, Firenze (nei pressi della località Due Strade). Parteciperanno il Teatro delle Ariette con Lettera ai Cavalli di Trieste di Giuliano Scabia e Pacifica Brigata Giuliano Scabia con Canto della vita indistruttibile di Giuliano Scabia, il sassofonista Dimitri Grechi Espinoza, la violoncellista Margherita Scabia e Annibale Pavone che interpreterà Apparizione di un teatro vagante sopra le selve, da Teatro con bosco e animali, Einaudi 1987.

Settembre

Il 5 settembre, presso Murate Art District (M.A.D., Piazza delle Murate), dalle 17:00 proiezione di filmati originali, tra l’altro sull’esperienza di Marco Cavallo (1973) e sul Drago di Montelupo (2003).

Il 19 settembre ore 21:00 al M.A.D. Sandro Lombardi e Annibale Pavone interpreteranno La luce di dentro di Giuliano Scabia, dal libro omonimo, Titivillus 2010.

Il 25 settembre ore 16:00 al M.A.D. Per un teatro dell’impegno, primo incontro con le realtà toscane che lavorano con il disagio e con la follia.

Il 26 settembre ore 20:30, in occasione del termine della mostra, al M.A.D., azione teatrale di Claudio Ascoli (Chille della Balanza), Lettere del filosofo Guido Calogero dal carcere duro delle Murate (febbraio-giugno 1942); alle 21:30 I sacchi di sabbia interpretano Cinghiali al limite del bosco di Giuliano Scabia, da Teatro con bosco e animali.

fondazionegiulianoscabia.it/te…

slowforward.net/2024/08/21/ago…

#follia #FrancoBasaglia #GiulianoScabia #ilDragoDiMontelupo #incontri #MAD_ #MarcoCavallo #MurateArtDistrict

Quelli di Basaglia... a 180 gradi | Estate Fiorentina

L'Accademia della Follia parteciperà all'Estate Fiorentina 2024 con lo spettacolo 'Quelli di Basaglia...

^{Giulia Misculin (Accademia della Follia - Claudio Misculin)}

A Napoli il 14 agosto 2024, i Carabinieri hanno arrestato un noto falsario, smantellando il suo sofisticato negozio di stampa contraffatta e sequestrando quasi 3 milioni di euro di banconote contraffatte di alta qualità.
Collaborando a stretto contatto con la Polizia Nazionale Francese, gli esperti delle rispettive unità di contraffazione anti-valuta hanno rintracciato il criminale ritenuto responsabile della vendita di milioni di euro di banconote false.
#Europol ha sostenuto questa indagine, iniziata nel 2022 e da allora ha visto i contributi dell'intelligence di almeno 10 paesi che avevano segnalato sequestri dello stesso tipo di banconote false in euro.

Laboratorio di stampa simile a Bunker in una residenza privata
Gli investigatori specializzati dell' #ArmadeiCarabinieri, con il supporto degli esperti di Europol, quando hanno fatto irruzione sulla nei locali oggetto di perquisizione, si sono imbattuti in una linea di produzione quasi industriale, contenente 31 macchine da stampa digitali e grandi quantità di materie prime utilizzate per la produzione di banconote false. Il criminale aveva creato un negozio in casa sua, nascondendo la fabbrica dietro il suo garage. Nascosto dietro un gabinetto, il falsario aveva costruito una parte mobile su rotaie, che gli ha permetteva di accedere al laboratorio di stampa tramite un sistema elettronico fatto in casa.

Le autorità ritengono che il falsario abbia fatto affidamento su diversi canali di distribuzione nazionali e transnazionali, quest'ultimo prevalentemente in Francia, per vendere le sue banconote contraffatte in denominazioni di 20, 50 e 100 euro. L'analisi degli esperti, inclusa una valutazione della Banca centrale europea, ha confermato che le caratteristiche di sicurezza contraffatte sulle banconote (come gli ologrammi) erano di alta qualità.
@Notizie dall'Italia e dal mondo