Met dit simpele wachtwoord haalde hacker gegevens van 8,8 miljoen Denen binnen


Iβve noticed when a zlib compressed chunk of data is followed by other data, search-for-compression.py will not always be able to detect the compressed chunk. This is caused by the fact that the other data generates a decompression error, and the complete chunk is disregarded.
Iβve added a new option to try to solve this: -S
Option -S takes a value, a positive number. Itβs the size of the decompression buffer. By default, its value is 0.
When you try -S 100 for example, search-for-compression.py will try to decompress up to 100 bytes. If that succeeds, then we assume that we found compressed data, and search-for-compression.py will try to decompress the remainder of the data until either a decompression error occurs, or there is no more data. But when an error occurs, search-for-compression.py will revert to the last decompression without error, and report that.
search-for-compression.py is still in my beta repository.

More info on this update: βzipdump.py: Metadata Encodingβ.
base64dump_V0_0_31.zip (http)
Unit 42 details how attackers exploit enterprise collaboration tools for identity phishing and credential theft. Discover key defense strategies.
The post Identity Abuse Through Trusted Communication Channels appeared first on Unit 42.



This new version adds option βstats. For more details, take a look at SANS Internet Storm Center diary entry βEvil MSI Background: BASE64 Statistical Analysisβ.
base64dump_V0_0_30.zip (http)