A few words about KRACK

You will have heard about the KRACK (Key Reinstallation Attacks) vulnerability. I think all information (even – as usual – some over hyped and misinterpreted) is available from many sources. If you are interested, I would recommend reading Mathy Vanhoef’s information on his website www.krackattacks.com.

However, here is a summary:

  • The WPA2 WiFi encryption has a weakness that can be used to sniff network traffic
  • Your WPA2 password can not be discovered by this attack, however it is not necessary for sniffing the traffic by using this attack
  • Almost all routers and WiFi Network devices are affected (including iPhones and iPads using the current iOS Versions)
  • This vulnerability can (only) be fixed with updates on both ends, Router AND Client

What to do:

  • Look for updates (for your Router AND your Clients). Throw away devices that can’t be updated.
  • Until updates are installed, prevent using sensitive information (e.g. Banking) on any WiFi device. Better use cabled devices for this.
  • If you really have to, double check if you are indeed using HTTPS while submitting sensitive information. Man-in-the-middle attacks, which are possible by using this vulnerability, will most of the time cause HTTPS connections to end up as HTTP connections in order to capture the traffic.
  • Carefully look out for unusual logins on your accounts or anything else unusual. In doubt, change passwords for accounts using cabled devices.
  • After everything calms down, take this opportunity to change all your passwords

Don’t trust the evil,




Next update 11.0.3 now available – UPDATE 2

After finishing and submitting my Update, I contacted Apple and asked for an Expedite review. Within one hour, Apple reviewed and released the App.

This was probably world record. A big thank you to Apple!


Unfortunately, there was a bug in the UPnP Scanning engine which was causing the App to crash when there is a ‘misbehaving’ UPnP device.

As this happened in the UPnP Scanning engine which is also used for the new Advanced Scanning feature, the new feature wasn’t working for some of you.

I hope that the new update will now work for you as expected.

To locate and fix this bug, it was very helpful that some of you enabled Crash-log submission in the Settings ( iOS Settings -> Privacy -> Analytics -> enable: Share Analytics as well as Share with App Developer). This way, I was receiving the anonymous crashlog via Apple and was able to analyze the cause. Thank you!

Have a great weekend (at least I will have one now as the update is out),



UPDATE Sunday 1st Oct:

In case some of you are wondering about the availability of the update, Apple currently has major outages. They maintained some of their servers yesterday, now claim that everything should be up and running but that obviously is not the case. Some support websites are not available and other Apple websites have wrong contents. So much to Apples world record of releasing Network Toolbox.

UPDATE Monday 2nd Oct:

Finally, the new update seems to be available after almost two days.

Thanks for your patience.



Version 11 of NetworkToolbox will be available Thursday!

Good news though. The new update will be available Thursday, September the 28th!

I have just updated the manual. For instance the chapters for Network Scanning and the new tools like Whois, DNS and UPnP. So if you want to see what’s coming, just have a look to these manual chapters.

This is, what has been changed:


► New WhoIs Lookup Tool (see details about any domain and who has registered it)
► New DNS Tool (query ANY! DNS Server for domains, see records and response times)
► New visual Traceroute (see trace routes on a map)
► New UPnP Tool (see which UPnP devices are noisy on your network)


► Extensive improvements of the Network Scanning engine
► Improved Morpheus Map
► Improved Bonjour Browser
► Terminal and SSH support for Backspace and CR/LF

Bug Fixes:

► Fixed Crash in External Apps Tool
► Special Keyboard Bar are now visible, no longer transparent
► Display of wrong MAC Addresses fixed
► Bug in MAC Database fixed which caused some Vendors not to be found
► Fixed bug in traversal test or Password test where entries, already tried were not marked accordingly

As always, this version was again a challenge. Please note, with iOS 11 MAC Addresses can no longer be displayed as the API has been removed by Apple for privacy reasons. However, the vastly improved scanning engine now combines many other information available about any IP Address on your network. This not just compensates the missing MAC address. Now you can see as much information as discoverable in one single place. Network scanning was never easier and more convenient before.

As this was again a major update with several weeks of development time, please consider to rate my App to keep it rolling.

In case you may find any bug, please let me know, I want to fix it!

Thank YOU!


Keeping you updated

Even though I provided a couple of Data updates, you might be looking forward to my next App update as it was quite some time ago, when I released my last App update.

As mentioned in my previous post, I will wait until iOS 11 has been released and then, shortly after, I will release a new App update.

However, I am happy to let you already know some of the features I have finished so far:

On this screenshot, you will notice two new tools: A DNS tool and a Whois tool. The DNS Tool will allow to query not just your default DNS Server but any DNS Server. This allows in-depth analysis of possible DNS issues. The Whois tool offers a lot of in-depth information about any domain. Most of this information is presented in a structured form (not as plain text as in some other Apps) so you can further analyze the results, as usual.

Furthermore, not to see on the screenshot, I finally finished developments for a Visual Traceroute tool.

And of course, I already fixed several bugs and added several improvements like support for Backspace and the ability to change the CR – CR/LF type in the terminal tools.

Looking forward for being able to release this Update soon.



NetworkToolbox and iOS 11

Last time, when iOS 10.2 has been introduced, the ability for NetworkToolbox to show MAC Addresses was no longer available as Apple has removed access to MAC Addresses due to security concerns and to increase our privacy. (see MAC Addresses are back)

It was a real challenge to find a workaround to be able to show the MAC Address again. My solution still works under iOS 10.3.3.

Now, with iOS 11 knocking at the door, you may wonder if it will still work. The answer is no. Unfortunately. Apple made my workaround unusable again in iOS 11.

I already investigated into this again for several days (and nights) but it seems, this time, Apple did a great job. They even fixed some additional (severe) security issues I found last time while I was looking for an alternative to get the MAC Address.

However, the consequence of this on iOS 11 is now, not only the lack of the ability to show the MAC address. The main disadvantage is, that I no longer can display the device Vendor, which is derived from the MAC Address using the internal MAC Database. This is and was a very valuable information while scanning a local network as it often helps to identify a device. Unfortunately, this is gone now.

I spoke to two Apple employees. Both told me, that Apple wants to protect users against Developers who misuse the MAC Address to track user activities and they said that this has precedence over the missing feature for my App.

I told them that this is a very good approach with good intentions but even without a MAC Address there are a couple of (even easier) ways to track user activities and, depending on the setup, a MAC Address can even be derived from IPv6 Address and that there isn’t much Apple can do against it.

I also recommended to add a security setting which could be used to allow/disable MAC Address access similar to camera or microphone access. So users can decide which App should be allowed to have access to the MAC Address.

One of these Apple employees told me that he is using my App quite often and found my statements and suggestions quite reasonable.

I am not sure (I even doubt) that my conversation with Apple will change the situation but maybe if more people (like you) would let Apple know, maybe it will.

Nevertheless, here are the plans for my next steps:

  • Shortly after iOS 11 has been released, I will create another Update of NetworkToolbox

(Shortly ‘after’ because I want to create an update based on and for the final iOS 11 version which makes sense as the App already runs just fine on iOS 11 (except for the MAC Address) and thus, wouldn’t require an immediate update)

  • I will give the MAC Address issue another (short!) try but will not waste too much time. Instead, I will polish the Network Scanning tool that it will provide as much usability as possible even without a MAC Address
  • Finally and in addition, that next update will include things, I already worked on (most of them have already been finished).


Thanks for your suggestions, which helped to make this App even better.

Stay tuned,



To Petya or NotPetya

You will have heard about the recent attack to Windows PCs called Petya or NotPetya.

The reason why some people say NotPetya is, that it is not a new version of the former Petya malware, even though it looks so.

This one is again (like WannaCry) based on the recently released NSA Tools (see my related post here).

But it is worse than WannaCry and was just built to create chaos and damage on as many systems as possible. The current damage is already massive. I bet you will hear more about it during the next days.

I will not repeat all the rumors about the source or intentions here.

Here is just, what I have done and what you should do (sorry, I should rather say “have to do”):

  • BACKUP BACKUP BACKUP (everything you don’t want to loose, your Pictures, Movies, Documents, Source-code, Letters, Tax Statements, Banking Documents etc.)
  • UPDATE UPDATE UPDATE (everything PCs, Routers, NASes, Mobile Devices)
  • Replace or switch off your Windows XP PCs
  • Do this on every Windows PC:
    • Start a command prompt with admin rights (right click on the Windows Icon in the lower left corner and select ‘Command Prompt (Admin)’
    • And type:

These commands will create three files perf, perfc.dll and perfc.dat and will mark them read only. The current version of NotPetya will stop working if these files were found. This is a very simple thing and most likely, a new version of NotPetya will disregard these files. However it doesn’t hurt and has no other side effect.

Finally, if you are already infected, for instance if you see a sudden Checkdisk message trying to repair your hard-drive or anything else unusual:

  • Immediately switch off your PC (even if Checkdisk says you should not)
  • Disconnect your PC from your network
  • Try to boot it stand alone. If this doesn’t work anymore, most likely, your data is lost.
  • Switch off your router / disconnect from the Internet
  • Check your other PCs as you might have a chance that they are not yet infected.


Don’t trust the evil.




NSA Tools available to everybody – Update your PCs. Quick!

As you may have heard, a Group called Shadowbrokers have stolen Hacking tools from the NSA and made them available to the public.

I had a chance to take a look at these tools. A few days ago they already released some tools but those tools were quite outdated and not really harmful if you don’t use an old Windows XP or Vista PC. But these new tools are indeed up-to-date and I was able to use the tools to compromise one of my Windows 10 PCs which hasn’t been updated for a few days. After it was updated with the latest Creators Update from Microsoft including all security updates, that was no longer possible.

The NSA Tools also include tools to disable or hide themselves against all known virus scanners, including Microsoft.

There are rumors that NSA has informed Microsoft about the fact that their tools were stolen along with information about the vulnerabilities these tools are using so Microsoft was able to fix these vulnerabilities. This makes sense as these vulnerabilities are existing for quite some time now and it is interesting that Microsoft has created these fixes before Shadowbrokers have released the Tools to the public.

About the NSA tools

Some people already asked if these hacking tools are indeed from the NSA or ‘just’ from Hackers. I have seen many similar tools by many developers and of course developed my own. The available tools have been developed in Java, Python and Perl, some are available as binaries.

Even though I found some humor like in the Zippybeer tool which contains an ASCII image like this:

I found the code really really well organized and straight forward. Typical hacker code contain typos, they often don’t really care about code quality and a lot of code I have seen looks really ‘messy’ or even contains messages to other hackers. This code looks excellent, very reliable and foolproof with a lot of try/catch and exception handling to ensure that the tools are doing what they are supposed to do or fail and let the user know why and not leaving a trace. This code hasn’t been developed in a rush and it is indeed professional, just like a commercial software. This is why I am pretty sure that it comes from the NSA.

What you need to do

So if you didn’t already, hurry and update your Windows PCs. If you are using older Windows Versions than Windows 10, disconnect them from the internet.

This is not because of the NSA as they may have already (or soon) finished new tools which will still be able to compromise your PC. This is mainly because these NSA tools are now available to the public. They are easy to use and I suspect not only by people with good intentions.

Don’t trust the evil.

Happy Easter.


Major CloudFlare data leak on millions of Websites – and Apps

CloudFlareNormally, you may find your stolen Email addresses and sometimes even stolen passwords in wrong hands because a certain website has been individually compromised – like happened with Adobe, DropBox or Yahoo recently.

Even though the Yahoo breach with more than 500 million affected user accounts sound like a major breach, a recent CloudFlare data leak has a new dimension.

CloudFlare is a service, used by millions of websites, to improve availability and speed. CloudFlare servers are working between the visitor of a website and the website itself and can be seen as a kind of cache.

What happened was, that since September 22nd 2016 and February the 18th 2017, CloudFlare had a bug which resulted in CloudFlare to respond back to the website visitor with memory contents of the CloudFlare servers instead of the contents of the visited website.

These memory contents often contain sensitive data of other websites such as API Keys, security tokens or even internal server and database passwords. Not only that this data may contain your personal data, even worse, with this information, the effected website and database can be compromised.

Things got worse as this leaked content has already been indexed by Search Engines like Google over the past Months. The issue with this is, that the data is now (still) available to everybody and can easily be found by using special Search terms. Google and other Search Engines are working on deleting such contents but it will be almost impossible to get rid of all leaked data.

Nick Sweeting provides a zipped list of sites (so far, he found more than 4 million sites) that are using CloudFlare which might be affected by this leak.

Not only Websites but also Apps (iOS and Android) such as FitBit and Uber are affected as they also use CloudFlare for data exchange. Data of such Apps have also been found by searching Google.

So what can you do?

Not much to be honest but you can take this as a gentle reminder to:

  • Change passwords frequently
  • Don’t use one and the same password for different services
  • Use fake accounts and fake Email addresses for registration wherever possible
  • Don’t trust the evil

Best regards,


Online shopping risks – check your store before placing an order!

Happy New Year everyone!

Yesterday, the German BSI warned (again!) about thousands of online stores worldwide which have been infected by online criminals in order to capture user’s payment data. Many store owner have been informed by the BSI some time ago but less than a half of them have fixed that issue.

Shopping on those still infected or unpatched stores is a high risk! Most likely, your payment data will end up somewhere else.

In 2015, Willem de Groot revealed this issue in the popular shopping software Magento which is widely used around the world.

Which scares me most is the fact that by that time, there were 3501 Stores infected, in March 2016 Willem found 4476 infected stores and late 2016 there were almost 6000 infected stores worldwide. Here is a list: https://gitlab.com/gwillem/public-snippets/snippets/28813

Fortunately, MageReport provides a tool, to check if a certain website is already infected or at least unpatched and a possible victim for cyber criminals.

So I would recommend to use that tool to check the online shops you are using before using them again.

I did so and guess what, three of them were infected – only one of them replied back to me after I informed them about their issue.


Don’t trust the evil!


MAC Addresses are back – Happy and secure Holidays

Today, Apple released my Update 9.02.03 which will bring back the MAC Addresses and fixes the Crash in the Device Tool reported by some users.

MAC Addresses

Bringing back the MAC Addresses was really a challenge and caused me some more gray hair and long nights during the last days. With iOS 10.2 Apple continued with their good intentions to protect our privacy by removing all sorts of information that might be misused by developers to uniquely identifying our devices. Apples approach is a good approach and I appreciate that in general. However, this has caused that I was no longer able to show the MAC Addresses in Network Scans anymore which was quite unfortunate as the MAC Addresses were also used along with the included MAC Database to show the vendor of each device. Finding a solution was really a challenge as I have to use official APIs because otherwise Apple would have rejected the App. The solution I found is indeed using official Apple APIs but in a very specific and unusual way (don’t want to elaborate more). This said, I expect Apple to even close this door at some point.

Device Tool crash

This was also a challenge. Some user reported the Device Tool to crash (one user even left a one-star bad review only because of this crash). I tried to reproduce this on any of my various test devices without success. Fortunately, some users contacted me regarding this crash (Thanks again!) and I asked those users to enable crash-log submission in iOS (Settings -> Privacy -> Diagnostics & Usage -> Automatically Send, then enable “Share With App Developers”). When switched on, Crash logs will be submitted to Apple and a few days (sometimes a week) later I am able to download anonymized logs from Apple. These logs showed that indeed for a few users, the App crashed for security reasons as it wasn’t allowed to access motion sensor data (Motion data will be accessed in the Device Tool for the Sensor section). The question is still, why only a few users were affected and why I was (and I am still not) able to reproduce this on all of my test devices. However, I hope at least I fixed this in the new version 9.2.3. If not, please let me know.


Thank you so much for all your reviews. It was overwhelming to read them all. Unfortunately they are now gone with this update but I don’t want to bother you again asking to update your review.

Instead, please have relaxing and secure Holidays.

Thank you all and let’s work together for a more secure 2017!

See you in 2017.

Best regards – and don’t trust the evil.


iOS 10.2 and missing MAC Addresses

Dear Users,

it seems that Apple has further improved their security measures in iOS 10.2. Unfortunately, this results in wrong MAC Addresses in NetworkToolbox.

I am currently working on a workaround so please be patient and wait for this fix.

Best Regards,


ALERT: Major attack to Routers. 41 Million Routers worldwide on risk.

alarmMajor attacks to routers are currently ongoing. These attacks already resulted in major outages of the German Telekom network and others in many countries.

The attack is using an old vulnerability on port 7547. This port is basically the interface for the Telecom companies to configure a router remotely. A variant of Mirai currently uses this vulnerability to install a bot using this interface.

Here is, what you can do:

1.) Restart your router

This will clean your router in case it was already affected. However, even after a restart, it may happen that the router will get infected shortly after by another attack as this attack is currently still going on.

2.) Check if your router is vulnerable

For this, you need to perform a reverse (from outside) Portscan on your public IP Address and Port 7547 by following these steps from NetworkToolbox:

– Select the Devices Tool
– Tap on Network
– Locate the Public IP Address
Take down this public IP Address (or bookmark to the Logbook)
Switch off (disable) WiFi mode on your device

Next, ensure that NetworkToolbox can use the Celular/Mobile network as follows:

– Quit NetworkToolbox
– Open Settings
– Tap on Celular Data
– Search for “NET-Toolbox” on the list
– Ensure that the switch for NET-Toolbox is switched ON


– Reopen NetworkToolbox
– Tap on the Portscan Tool
– As Address, enter the Public IP address you took down previously
– As Port enter 7547
– Tap on Scan

You should get an empty list (0 Results). If that’s not the case, your router might be vulnerable.

3.) Protect your router

First of all, you should look for a firmware update. German Telekom currently provides an update for the effected router which is installed automatically after restarting the router. Other may need to look for a router update on the suppliers/vendors website.

After an update has been installed, I would recommend to perform another portscan.

In addition, I suggest to disable this port if possible. Some Routers, like the German Telekom Routers, offer an option to disable the remote configuration feature which will also disable port 7547. On the German Speedport routers this feature is called “Easy Support”. On other routers it might be called “TR-069” or similar.

I would suggest to switch this feature completely off. Please note: if you are using a rented router, your provider may not be happy about this as they can no longer look into your router in case of issues.

Once the port can not be accessed from outside, you should be safe.

Some more background information:

As mentioned before, port 7547 will be used for remote access configurations on your router using a so called TR-069 interface. This interface is quite safe as it uses a callback feature that ensures that only the valid provider can access and change the configuration data.

This interface will also be used for instance by a Synology NAS if you would allow the NAS to configure your router on your behalf for convenience.

However, due to a bug in older implementations of the TR-069 protocol, this interface can also be used for code-injection.

So an open port 7547 alone does not mean you are vulnerable but along with a buggy firmware you are.

Then, either updating the firmware or disabling TR-069 (or closing the port if the router offers such a possibility) would fix a possible issue. If possible, I would suggest to do both (updating and closing the port).



Mirai and Yahoo


You may have heard about the biggest DDOS attack ever against my colleague Brian Krebs. Brian’s Website has been attacked by devices on the internet which have been compromised by a malware called Mirai (please visit Brian’s website for more details).

I read the source code of Mirai and developed a new security check for you which will be available in NetworkToolbox after checking  for the latest data update in the settings. This new security check will scan for the same vulnerabilities Mirai is using to infect devices.

So you may want to run this security check on some or all of your network devices. If the security check reports a certain device is vulnerable, it doesn’t mean it is already ‘infected’ by Mirai but if Mirai would by chance pass by and visit your network, it is most likely that it will infect that device.

According to what I have seen while inspecting the code, fortunately Mirai will disappear once you restart the infected device. So what you should do, once the new security check reports a vulnerable device is, to restart that device and either remove it from your network or try to update it’s firmware and perform another Security check.


You may also have heard of the latest news about Yahoo.There are three strong arguments why to leave Yahoo as soon as possible:

  1. As mentioned in previous posts, Yahoo is about to be sold. Most likely to Verizon. You may also remember my post of Verizon’s Super-cookie.
  2. 500 Million Yahoo accounts have been hacked.
  3. Yahoo has scanned all mails for NSA and FBI.

A single fact from the above list should be enough to say good bye to Yahoo but I am still surprised to receive many Questions and Support mails from user with Yahoo accounts.

A few weeks ago, I was about to block all Yahoo mails as this would reduce the amount of Spam mails quite a lot (Spam is probably a fourth reason against Yahoo). But since I still receive so many Yahoo mails, I decided against blocking yahoo.

Your question might be, what else should I use? Google? Definitely not! Keep in mind (and this applies very much to Yahoo as well): “Nothing is for free”. Think twice: why should a company who needs to earn money to pay at least their employees offer a service such as Email for free? If you want security, you have to pay – period.

My best advise is, to look for one of the many service Providers who offer simple web-hosting and Email services for a good price and (most important) with a good reputation. Such a provider can be used to register your favorite domain name such as your surname (or combinations like surname-city.com for instance) and they can run a well working Email service for you. This way, you will have personalized and nice Email addresses combined with a reliable and secure Email server. Such (good) providers will also take care of Spam and While/Black listing. Often way better than the big guns like Yahoo or Google.

For a temporary time, you can forward your Yahoo (or Google) mails to this address.

Don’t be trust the evil.


The Connections tool is gone – which is good!

A very provocative title isn’t it? But yes, it’s true, it is good. I will explain why.

I have received a couple of support mails regarding the no longer working Connections tool. Some people were just wondering when it will come back. Some are blaming Apple for it and one unpleasant person even had nothing else to do than blaming me with loads of unpleasant words and sentences that I don’t want to repeat here (but I will if this person doesn’t stop this).

So what has happened ? I am usually testing compatibility of my Apps with pre-release versions of iOS. In case some action is required I will prepare an update. At some point, Apple released a pre-release that prevented the Connection tool to work. Often, such thing happened and with further pre-releases things get back to normal – and so it does. The Connections tool started working again. But later, with the latest Release Candidate of iOS 10 it discontinued to work again so I started investigating why.

It turned out that Apple has completely removed an API I was using to generate the connection list for the Connections tool. By that date, I investigated in many alternatives which all turned out not to work (anymore or not at all on an i-Device). That was sad as I am also using this Tool quite often, whenever I like to analyze suspicious behavior of newly installed Apps and often discovered bad “calls home” or other undesired connections (e.g. Flurry).

On the other hand, while implementing the Connections tool some time ago, I was even surprised that Apple did offer the API in question as it also allows many other even bad things to do. Other Apps can and likely may have already used the same API for other, undesirable purposes. After implementing the Connections tool and submitting the App to Apple, I also expected that Apple will reject my App – which was obviously not the case.

The problem here is, that even though I call it API, it’s not really a typical “officially documented” API. It was rather a system call with very specific parameters. Such a system call is hard to identify within the review process and that’s probably why. But as mentioned before, this system call can also be used for many other things I definitely don’t want another App to do on my iPhone or iPad.

So even though it’s sad that the Connections Tool can now no longer be used, it is good that this particular API (or System call) is gone. This is indeed a real gain in security and I am hoping Apple will continue to walk this Path. I think it is way more important that our i-Devices can not be compromised and that bad Apps can harm our security and privacy and I think it’s worth the disadvantage that we now no longer have a Connections tool available.

I think Apple is doing a great job by not only continuously adding new great features but also care for security. This is why all my Android Devices (I have quite a few since I used to develop Android Apps as well but discontinued some time ago) remain in my drawer and will not be connected to my internal network. Those devices are quite insecure and exactly the opposite. Google doesn’t care about security and they are even the worst data spy themselves. A Connections tool for Android would still be possible of course but I would not trade any Android Device with any of my iPhones or iPads.

So as you can see, it is very unlikely that the Connections Tool may come back in the future but there is no reason to complain about Apple. They did their job well.

I leave it up to you to decide if it is me who needs to be blamed.

Don’t trust the evil!










New Update available!


A new version of NetworkToolbox is available.

The new version contains various changes, additions and fixes:

■ Renewed Bluetooth Tool

I have completely re-written the Bluetooth LE scanner. It is now more reliable and easier to use.

■ New Health Check Tool

This new Tool can be used to perform recurring pre-defined tests. You can add multiple sites (IP Addresses or hosts) and perform Ping, Certificate, Mailserver and other tests with a single button press. This way, you can quickly check the availability of components either in your home network or your Internet Servers.

■ New SMB Tool

You can now even browse Windows or other Samba shares using this new Tool. It is also possible to download files.

■ New Speed Test Tool

This new Tool implements the iPerf Speed Test standard and can be used to perform Network Speed/Bandwidth tests to one of the public iPerf Servers or even between two NetworkToolbox Apps running on the Network since the Tool also provides the possibility to run an iPerf Server.

■ Further improved network scan

Now, SMB Network Names and Vendor Names will be displayed in the list itself and not only on the detail screen.

■ Export Settings

As requested, you can now export the settings either for backup purposes or to submit the settings (including the user passwords etc.) to another iOS Device.

■ Reverse DNS and DNS Lookup improved

Even though the Tool is still called NS-Lookup, it is now rather a multipurpose tool that shows all kind of information available to an IP Address or host such as DNS Record information, Revers DNS Lookup, Provider information and more.

■ Macros for Telnet and SSH

It is now possible to write and maintain Macros that can be submitted from inside the Telnet or SSH Tool. Macros also let you sent special Key combinations and supports delays.

■ Other Telnet and SSH improvements

The Keyboard window will now only cover the necessary part of the screen and in case you are using a hardware keyboard, you will now see the full telnet/ssh screen.

Now you can also directly send special keys that are not available on the software or hardware keyboard.

■ WOL (Wake on Lan) has been built in

■ HTTP Head Tool improvements

This Tool now also shows the Status code returned from the Server and an explanation of the meaning this code.

■ IPv6 support

Most Tools now support IPv6 where appropriate. If available, you will see IPv4 as well as IPv6 addresses in the result lists of several tools. You can also enter IPv6 addresses in several Tools in the same way you enter IPv4 addresses.

■ New IP Calculations

With the introduction of IPv6 Addresses, there are also three new Calculations for the IP-Calculation Tool such as IPv4 to IPv6, 6to4/6RD and Teredo calculations.

■ New Manual

As you may already know, this App contains a lot of information and help texts with general information as well as for each individual tool and how to use it (Thanks again to Martin who helped me out here). Several users appreciated that but asked for a separate manual so they can read it side by side with the App. This is now possible. I have moved the existing content and added some more text to a separate manual, which can also be opened from here: http://go-to.me/nettb-manual but also still from inside the App by hitting the (i) button as usual. If you prefer a printed version, you can also download the manual as PDF file.

■ Bye-bye to the connections Tool

With iOS 10, Apple has removed an API which has been used for the Connections Tool. This means, that this tool no longer works under iOS 10 and you will get an according message if you try to use it. Even though it is not nice that this valuable tool now no longer can be used, Apples decision is a major increase on Security as this API could have also been used for other purposes by any App.

■ Other bug fixes and improvements

Besides the lost Connections Tool, NetworkToolbox is now fully compatible with iOS 10 and even uses some of the new advantages. On an iPad Pro, it can also run in Multitasking and Split Screen mode and it runs just fine on the new iPhone 7 devices.


As you can see, there were many changes with this new Update. It even took quite some time as due to IPv6 Support major parts of the App needed to be re-written.

This said, I wouldn’t be surprised if me or my valued Beta Testers would have missed one or two Bugs. Please don’t worry and just let me know so I can fix it timely.

Updating this App means that it will lose all your nice and kind reviews.

So please, after you installed the update, update your review as well or write a new one.

I hate these annoying nag-screens reminding users to write a review and don’t want to include that.

For your review, you can also tap here.

Thanks for your great support!


Kind regards,


New Manual and new Version soon

Today, I am happy to announce the new Manual which is now already online for you from here:


Several users found the included (i) Help texts useful but prefer to have the description side by side on another screen or even paper – which makes sense. This, I created the online manual.

Please note: This Manual already covers the next version with many new features and improvements. This new version will have this manual already included also from inside the App but I found it might already be useful for all users of the existing App version.

While talking about the next version. It took quite some time to get it done. This was basically because I had to re-write major parts of the App due to the fact that it now also supports IPv6. There are still some parts of the App which don’t fully work with IPv6 due to some oddities in iOS but I will either fix this during the next days or will leave it as is by now assuming that the majority of you will still use IPv4.

So please stay tuned for my announcement for the release of this update,
Best Regards,

NetworkToolbox with wired Ethernet connection – not only WiFi anymore! – UPDATE

network-toolbox-and-ethernetSometimes, you may whish to connect to a network via Ethernet Cable in order to inspect or analyze a network. So far with NetworkToolbox it is only possible to connect to a network via Wlan/WiFi.

But there is good news today!

For this reason, some time ago, I bought me the Lightning Ethernet Cable (L2-NET) from Redpark. This cable requires some developments as it’s not supported by any iOS Device itself. I also had to register for Apples MFI Program which is necessary if you want to ship an App which uses a hardware accessory. I did that and I also did already develop almost all necessary changes for NetworkToolbox which was quite a lot as all network routines (especially the scanning and sniffing ones) will have to be adapted for this cable. Unfortunately, at the end, it turned out that the provided Library had some bugs but moreover the Cable often ended up in a situation where I had to completely re-start the device which was the reason why I never released this feature. I was in contact with Redpark a couple of times. They were very kind, committed and helpful but at the end it turned out that the cable issue cannot be solved at least not for NetworkToolbox. If this would change in the future, I will be more than happy to support this cable as I really like it.

However, here is something new:

You can use the new Lightning to USB 3 Camera Adapter along with the USB Ethernet Adapter.

The USB 3 Camera Adapter, which is basically a USB 3 Adapter, was introduced for the new (big!) iPad Pro (the new small iPad Pro doesn’t support USB 3 by the way). I wanted to buy this adapter for my big iPad Pro anyways but added the USB Ethernet Adapter to my order – just in case.

Once the package arrived, I tried to connect both Adapters together and plugged them to my iPad Pro. Then I got a message saying that the Ethernet Adapter consumes too much power and cannot be used.

Two things where surprising with this message: 1.) I didn’t get the usual message saying that this device is not supported, 2.) It even recognizes the second adapter as an “Ethernet Adapter”.

I then put a regular USB hub in between the two Adapters and provided power to the HUB.

Success !!  – as a result, I didn’t see any message anymore but also nothing else. No confirmation message, no additional menus in the Device settings (as it was the case with the L2-NET cable).

Then I switched off WiFi and Cellular, started NetworkToolbox and to my surprised, the Adapter was found and I even got a DHCP Ethernet Address. I was also able to Browser (real fast!) and perform Network scans with NetworkToolbox – pretty cool isn’t it ?

Next, I tried the same with other devices and found that at least my iPad air 2, iPhone 6 and 6s are working well. There may be others working as well but I have not tried it yet.

I then tried to use other HUBs and found that almost all I have are working, except for one old HUB.

I also tried different USB Ethernet Cables which all didn’t work.

I did not try but this solution may even work with the old iPhone Camera Adapter.

So in short, here is what you need:

If you plug all together and power the USB Hub, switch your iPad/iPhone to Airplane Mode (to disable all other communications), wait a few seconds and then try to use Safari to see if the connection is working. If not, double check the HUB or try another HUB.

Even though NetworkToolbox reports a local IP, it reports a public IP and correct DNS Server and is working very well with this solution.

Please let me know if anybody of you is successfully testing this solution on other devices, or even found that the old Camera Adapter is working well so I can update the compatibility list on this post.

UPDATE: Cristian from Gibraltar just reports that the old USB Camera Adapter works as well with the Ethernet USB Adapter. Thanks Cristian!

Don’t trust the evil!
Best Regards,

Email tracking even on your iPhone

A dear user and contributor of NetworkToolbox just raised a point I would like to share with you.

While discussing my arguments against Web-Mail services and my suggestion to rather use a Mail client instead, he mentioned that he got frightened some time ago even while using his iPhone mail client. What happened was, that he received an Amazon gift voucher from a relative and while he wanted to thank him five minutes later for the gift, the relative told him that he already knew that he received his gift because he’d just received an email from Amazon informing him about it.

So you may wonder how this could have happened even on a relative secure Apple device. The trick is quite simple and widely used by many newsletters, eCards and even regular mails.There are many service providers offering such a feature to companies even garnished with sophisticated statistics about reading time and even the location of the recipient.

What the do is, they just add a small image (visible or not) to each email. This image has an individual name which is different for every recipient. Once the email has been opened, the email client tries to download this image from the server in order to show the email right.

The Server, where the image comes from just responds with the requested image, maybe an empty 1×1 white pixel. So far so good. But any Web-Server, and the server for such an email image is also a Web-Server, will see the requesting IP Address and, of course, the file name of the requested image. Remember, as mentioned before, the file name is basically a unique Identifier which identifies each recipient and the IP Address will help to track down the location and other information such as type of device (e.g. iPhone) as well as the client software the recipient is using. And of course, all of that is being logged and can trigger an email to somebody who is interested in knowing when you read their mail.

But for iOS users, it’s not too bad at all. There is something one can do against it what the dear user found out on his own while googling. There is a setting under Email settings called “load remote images” (or “Bilder vom Websever laden” for the German users) which should be switched off.

It is very unfortunate that this setting is turned on by default but I would strongly recommend turning it off. This setting will prevent the things I mentioned before from happening. The only disadvantage is, that some mails might look a bit strange without images which will no longer be loaded in the future once this setting has been disabled but it’s often not too bad and you can manually force the images to be reloaded. But then, keep in mind, the sender may (and most likely will) track this.

You may wonder why you see images in mails even while “load remote images” has been switched off. The reason is, that in that case, images have been embedded in the mail and thus, don’t need to be downloaded and thus, can also not be used for tracking. The disadvantage for this approach is, that such mails get bigger, are causing more network traffic while sent out and while downloaded on your device.

So, don’t trust the evil.
Stay safe!

The worst thing happened

ns-image2What is the worst thing to happen with regards to network security you can imagine?

How about a network device that should care for your network security which has a back-door that allows access by everyone from everywhere? Yes, that’s scary, right?

Exactly this has happened to Juniper users – and we all are affected.

For your information, Juniper is the second largest company selling Routers, Switches, Firewalls and other network products after Cisco. Their products are widely used from small businesses, large companies, Network providers to governmental networks.

Recently Juniper indicated that they had discovered unauthorized code in their ScreenOS software used in their Netscreen firewalls. It turned out that this code contains two back-doors which allows full device access and VPN traffic monitoring. Further investigations revealed that all of their firewalls running software versions shipped from 2013 until recently can be accessed from everywhere by everyone via SSH using any username and password “<<< %s(un=’%s’) = %u”. An update will fix this issue.

So far, it is unknown how this backdoor slipped into their code.

Currently, Morpheus and Shodan finds more the 30.000 of these devices.

Maybe you personally don’t use Juniper hardware but be assured, your Provider, Bank, online Store, Company you are working for may likely use Juniper hardware.

It was good that Juniper offensively informed about their findings so that security researchers were able to start their own investigations. However, it took two years to find the back-doors. My personal assumption is, that organizations like NSA, GCHQ, Asian or Russian organizations are responsible for this and moreover, I further assume that similar Back-doors are available in other Network Devices such as those from Cisco and other “big Players”.

I even now see the other Back-doors I mentioned in my blog (here and here) from a different perspective. Not unlikely that these back-doors were not results of brain-dead developers but have the same source.

Regardless whether my assumptions are correct, many networks are currently at high risk. Even more because not only NSA, GHCQ etc. are able to access our data, now even inexperienced criminals can.

Due to the impact of this issue, there is not much one can do other than to follow following rules that make sense regardless of this impact:

  • Think twice if you have to give out personal information such as Name, Address, Email Address and payment information. Better enter it for every single transaction rather than let your online shop conveniently store it
  • Use strong passwords and change your passwords regularly
  • Never use one and the same password for different services
  • Never use one service to log into another service (e.g. don’t use “Login with Facebook” for Netflix)
  • If possible, create some fake accounts and fake identities and use them instead of your real accounts where possible
  • Leave Yahoo. If you still have A Yahoo account, close it. Not unlikely that Yahoo will be sold soon so your information might end up somewhere else
  • Better don’t use a public WiFi network without VPN. Rather use your Cell network (3G/4G/LTE) when security is important
  • Use Firefox instead of Internet Explorer
  • Use Ove’s Self-Destructing Cookies plugin or similar in your browser
  • Setup your mail clients to use encrypted passwords and SSL/TLS
  • Better don’t use Web-Mail clients (except for your fake accounts)
  • Never ever use Android devices
  • Never ever use Windows XP anymore
  • Always install updates (for Software and Hardware)
  • Always change default passwords
  • And of course, consider NetworkToolbox to check for security issues

Of course, there is much more we can do but most of the above is either easy to do or simply mandatory and without alternative.

Regardless, I wish you and your families a Merry Christmas and all the Best and secure 2016!


Linux cheat sheet added

As requested (and to be honest also for my own sake) I added a linux cheat sheet to NetworkToolbox.

This additional information resource doesn’t cover those simple and basic Linux commands. Instead it contains many less known and easy to forget commands, especially for network administration and information gathering.

If some of you are interested even in the simple commands, please drop me a line and I will be happy to add those as well.

In order to install this cheat sheet, just perform a data update by heading to the settings screen of NetworkToolbox, scroll down and press Check for data update.

After the update, you will see a new Icon in the Resources section of the App which contains the new Linux cheat sheet.

Cheat sheet


Security check added for the recent Netgear security flaw

I assume you have heard already from the recent findings of exploitable Netgear routers.

If not, here is a brief summary:

Due to another ignorance or security in-awareness of developers of the Netgear router firmware, it is possible to access several (thousands!) Netgear routers from the internet without entering correct credentials. For details see here.

If this alone isn’t scary enough, Netgear has again to be blamed for their slow and ignorant response to this serious security flaw.

Even though Netgear has finally released an update that fixes this issue, still thousand of routers can by found using Morpheus or Shodan which still run the old firmware and thus are exploitable.

To check if your own router is affected, I have written and just release a new security check for NetworkToolbox which can be downloaded by running a data update from the settings screen of NetworkToolbox.

After downloading, you will find a new entry called “Netgear router exploit” in the Security Check tool.

So, better check yourself with NetworkToolbox and don’t trust the evil.



The truth about XCode Ghost – UPDATE

XCcode Ghost

See my update below.

As this already goes around in the news and not only in the technical press, you will have heard about the XCode Ghost issue and the so claimed “Apple’s biggest malware attack”.

What happened is in short: Some developers, mainly from China downloaded the so called XCode development environment, which is required to develop Apps from dubious websites instead of Apples official website or Apples App Store. The version they downloaded was infected and so were the Apps produced by this XCode version. Some Apps made it to the App Store and some are still available for downloading.

So far, so bad. Scary, isn’t it.

No, it’s not that bad.

Unfortunately, the press and even the people from paloalto networks who “revealed” this story first are currently mystifying this subject rather than informing fully and correctly. They even provide misleading and even obviously wrong information.

So here is my story:

I personally found one of the effected Apps on my device (CamScanner this App has yet been removed from the Store so I can’t provide the link). I reverse engineered this App and can confirm that it indeed contains the XCode Ghost “Virus”.

Further investigation of the code revealed that this code is almost harmless. At least as harmless as all the damn Flurry, AppCrashLog, UserActivity Libraries I am complaining about for quite some time.

It “just” collects even less than Flurry does and submits it to a server (init.icloud-analysis.com). There is DEFINITELY NO key logger included, NO POPUP will be displayed that asks for an Apple ID/iCloud access or something similar. The rumors about this are absolutely wrong.

Of course, the code could have been more dangerous and my finding depends on just one App so this is not an “all-clear”.

However, most likely it is not as bad as the press writes. There is no prove (maybe yet) that there is any App “infected” in a way that user’s security is affected.

The reason why I am very confident about this is, that I was able to find the source code on the Internet which is 100% identical to the code I found in CamScanner and that also fit’s 100% to the story of paloalto networks. That source code is also garnished with a Chinese “excuse me” of the developer who is claiming to be the author of XCode Ghost.

Take a look yourself here: github.com/XcodeGhostSource (maybe use Google translate to read it)

Until there is no further prove otherwise, I assume that this is exactly the code which is included now in some Apps on the App Store.

Apple is currently trying to identify these Apps (which should not be too difficult) and removing them. I however would also expect a list of these Apps from Apple (not like the one on the paloalto website which contains spelling errors and App Names that are available several times on the App Store) so we know which Apps may still reside on our devices.

For your information, and that’s also missing in all the other press statements, you just need to delete the App and it’s gone. There is nothing that remains on your device after you delete it.

And here is, what you can do as NetworkToolbox user:

As explained earlier, my App contains the recently introduced Connections tool. This is ideal to identify such unwanted connections. I just wrote a small tutorial which explains how to detect XCode Ghost using NetworkToolbox.

You may wonder what Apple can do to prevent this from happening in the future. To be honest, so far, there is nothing to blame Apple for right now because (as mentioned before) this code is “harmless” in terms that it doesn’t access secured information and it doesn’t use private APIs. Otherwise I would have been quite sure that Apple would have rejected the Apps (as happened to my Apps).

The most people that have to be blamed are the developers that downloaded XCode from the dubious websites and used it for submitting the Apps to Apple using it. The same thing could definitely have happened on the Microsoft Platform. Maybe even easier because Microsoft does not offer some real App Store approval process at all.Not to talk about Android where there is no protection at all for way easier kind of injections with way more uncontrolled device access.

But I guess, Apple will now most likely speed up and shorten the grace time period for developer of Apps that now have to use HTTPS/TLS rather than HTTP and need to announce and name all domains that their App connects to.


For long time, it seemed that I am the only one claiming that XCode Ghost is relatively harmless. All the so called ‘Security Researchers’, the big press like the German ‘Tagesschau’ and even Heise never got tired of repeating the same story that XCode Ghost has been the biggest hit to iPhone App users security ever and everybody is at risk.

Recently also FireEye (who already is one of my friends) was dared to say that they experienced some MITM (Man in the middle attacks) and offered to “protect their customers” against XCode Ghost.

I sent a lot of mails to those researchers and companies telling them that they are wrong in their assumptions and that they should spend a few minutes in analyzing the code. Probably that was either too difficult for them or they just didn’t listen.

For instance, I asked FireEye what the heck they think how MITM attacks could compromise the users of Apps with XCode Ghost. No answer. Dead end. Probably because the answer is, it makes absolutely no sense at all.

There are still numerous false alarms regarding Phishing and Clipboard interception capabilities of XCode Ghost.

Unfortunately, this all was said by inexperienced, unthinkingly, ignorant, arrogant and attention addictive so called security researchers and the unfortunate so called “press” and security websites just copied and pasted their wrong conclusions.

For me, this is definitely the real issue with XCode Ghost.

Anyway, I gave up repeating the truth about it, hoping many people will read this post and come to their own conclusion.

But it was nice to see that I am finally not alone with my conclusions. See here:


Don’t trust the evil!



Check for ATM Skimmers with NetworkToolbox

atm2Nowadays, ATM Skimmers use Bluetooth to transfer your stolen credit/debit card details and PIN code.

Brian Krebs today talked about this in a great story where he visited some Hotels in Mexico (even one I stayed in a few years ago) and found several Bluetooth Skimmers.

The hacked ATMs are using Bluetooth modules that are used to download the collected data from the Skimmer inside the ATM. This way, the criminals don’t need to get very close to the ATM to download the stolen data.

Even though this is another scary escalation of the Skimmer technology, the Bluetooth modules can be discovered even by NetworkToolbox. The Modules Brian found are standard Bluetooth modules from a company called Free2Move and that’s also the name these Bluetooth devices are propagating.

There are Bluetooth Modules available for Bluetooth 1.0, 2.0 and even 4.0 (LE) so you will have to discover all three standards. Bluetooth 1.0 and 2.0 devices can simply be discovered by going to the Settings screen of your iPhone, select Bluetooth, switch Bluetooth on if it’s off and wait if your iPhone discovers new Bluetooth devices around you. If you see “Free2Move” when standing close to the ATM you may better want to look for another ATM.

For Bluetooth 4.0 or Bluetooth LE (Low-Energy) you can use the Bluetooth Scanner which is included in NetworkToolbox (Please note: you need to have at least an iPhone 4s for this). Just run a Scan and check the names of the discovered devices and look for “Free2Move” or anything else that doesn’t look obvious.

Of course, the Criminals can change the name but so far, the Skimmers found by Brian Krebs can be discovered this way. At least I will try it whenever I am using an ATM and will let you know once I find a Skimmer or once I got suspected as criminal when standing in front of the ATM and do my scanning ;-).

Don’t trust the evil,

have a secure day,






WordPress WPML Multilingual plugin – better switch if you still use it

This story is not really related but I had to write it. Simply skip if you don’t use WordPress.

I am using WordPress for most of my Websites and some time ago I purchased the WPML plugin for easier handling of multi-language pages. This plugin wasn’t cheap (about 200 Bucks) but I thought it’s worth it. Little later, after using WPML for a while and after almost getting used to the cumbersome UI and weired bugs, I heard rumors about security issues with WPML. So I looked for updates and headed to their support forum. After reading that they are not really able to fix these issues soon because of issues with their update procedure, I took a look into their PHP code. After this, I knew I have to disable WPML immediate and switch to another solution.

It took me quite some time to find and migrate to another solution but thanks God I did. Later I forgot about WPML.

A few minutes ago, I received the following mail:


So in that mail WPML claims that they updated my password to a strong and secure one (I always thought I am using strong passwords by the way). Further down, they sent me the new password in plain text and EVEN added the Login name (for my convenience I guess) to that mail.

But it got worse. When inspecting the included link they added to the login page (probable even for my convenience) I found it contains the address of a redirect PHP on a completely different server.

At that point, I was pretty sure that this must be one of those usual phishing mails and just in case, I sent a mail to WPML (using the contact form) to inform about this.

Seconds later, they confirmed that this mail was real.

Isn’t that unbelievable ?

I think this finally proves that WPML definitely has no clue about security. So everybody who is still using WPML (probably not too many still) now know that they better switch to something else.

As a site note: WPML can be found on WPML.org which is ok. But WPML.com is available for sale. Imagine what happens if a bad guy would acquire WPML.com. But it’s not cheap I must admit.

Anyways, don’t trust the evil.

Best Regards,


Should we uninstall anti-virus software such as Sophos, ESET, FireEye and Kaspersky ?

Regular readers of my blog know that I am no fan of anti-virus software.

Now, here is another argument against them. Tavis Ormandy recently exploited successfully Kaspersky in a way that users could find their systems easily compromised. Just recently he did the same for Sophos and ESET and even this Sunday, Kristian Erik Hermansen disclosed a zero-day vulnerability in another Malware protection solution from FireEye, which if exploited, results in unauthorized file access.

My personal opinion is that the good old days for those companies are over. Instead of continuing to invest in good security engineers and software developers, they spent their money rather for advertising, fighting against their competitors and seeking for additional ways to make money.

I guess all of you had once your own issues with your preferred virus-scanner or security suite (how they are nowadays called). Dramatical slow-downs, unreachable websites, odd browser behavior, undelivered mails or completely messed up firewall rules. All issues that suddenly disappeared once you switched off or uninstalled the virus scanner. Don’t you ? And for us network admins, isn’t it always scary when the preferred scan engine on the server gets updated because you still remember the server outage due to such an scanner update.

But you thought that this is the price we have to pay for increased security. Now we have learned that we even loose security when using Anti-Virus software.

My suggestion: Don’t use them! Stick with the built-in security measures of Windows, Mac or Linux. Use a good router, use NAT, use Firefox (or if you don’t like Firefox use Chrome for God’s sake) but always keep everything updated. This is all you need for regular browsing and working. The built in Windows defender for instance is not too bad at all. Even though those brave computer magazines regular tests show it never #1 in scanning accuracy. A few pages later you can learn why when reading the big advertisings of these Anti Virus companies.

In addition: if you have to visit suspicious websites or servers or need to access dubious systems or have to do some downloads and to unzip and install files from insecure sources: Never ever do this on your production system. At least setup a virtual machine or better use a separate computer running on a separate IP address space. This is easy to do, easy to recover in case of issues and the best protection you can get.

Don’t trust the evil,

Best regards,










Babies and families at risk!

Maybe this is another bad coincidence. Shortly after my findings regarding the quite insecure ALDI / MAGINON web cameras, Rapid7 informs about IoT security issues, especially about 10 New Vulnerabilities for Several Video Baby Monitors.


There is nothing to add to this scary report except that this is just again another example of incompetent developers, IT and quality assurance departments of ‘well known’ companies. I hope all of them get fired but maybe they deserve something worse. For instance, that their family or kids get stalked. No – This is something we should not wish to anybody. This would be wrong. But they didn’t seem to care about your family and privacy.

To check your own devices, I just updated the default password database of NetworkToolbox accordingly.

Don’t trust the evil!


P.S. NetworkToolbox now has it’s own dedicated Facebook page.

Ins0mnia and NetworkToolbox

You may have heard about about Ins0mnia which is a security vulnerability that allows an iOS App to continue to run in the background, even if the App was terminated by the user and not visible in the task switcher. Security researchers argue that Apps that are using this Ins0mnia vulnerability may even be able access the microphone or camera without your knowing.

As an App developer I can tell you that camera access is not possible in the background and both microphone and camera access will only be possible if a user acknowledged the request to access those peripherals. Without a user confirmation, even an App using the Ins0mnia vulnerability can not access microphone and camera.

But anyways, the Ins0mnia flaw is not good but it’s good that Apple fixed this security issue with iOS 8.4.1 (so hurry, if you didn’t already update).

So what about Ins0mnia and NetworkToolbox ? Can NetworkToolbox detect Ins0mnia ? I would be scared if that could be the case to be honest. Because that would mean that Apps would have access to other Apps out of it’s own Sandbox. This is only possible on Jailbroken devices and that’s why Jailbroken devices are quite insecure.

But NetworkToolbox can indeed help. With the recently introduced Connections Tool you can find out, if one of your Apps “calls home” which means if it sends data from your device to another server on the Internet. As already mentioned, I created a small tutorial which explains how to do that.

But it’s even easier with Ins0mnia because the nature of Ins0mnia is, that it continues to run in the background and also communicates over the network while in the background.

So here is, what you can do (not only to detect Ins0mnia) :

First, you should close all Apps on your device (double tap the home button and swipe all Apps to the top one after the other).

Then, start NetworkToolbox and open the Connections tool. Normally you will see about 10 to 15 connections. If you wait a while and press the refresh button, this number should go down to about five or even three. If you take a look at these few connections, you should only see Apples IP Addresses (those starting with 17), maybe the IP Address of the mail provider you are using and maybe some akamai domains. That should really be all you see after a few minutes. If you see more and different addresses, it’s worth to inspect them because that’s unusual and can be caused by an App using the Ins0mnia vulnerability.

Don’t trust the evil!

Best Regards,


New Version 8.2.1 now available

The next version 8.2.1 of NetworkToolbox is now available.

I hope you will be excited about the new features.

Please note: Don’t forget to check for a Data Update also.

So here is what’s new:

  • Introduction of Public / Private keys

The SSH and SFTP Tools now supports Public Private keys for a more secure connection. As key maintenance is usually not so easy, I also added a separate Tool for maintaining your keys. Finally, you can even generate all kind of keys from inside NetworkToolbox. To encourage more people to use Public/Private keys, I wrote an easy to follow tutorial which can already be found here.

  • A Connections Tool was added

This tool can be used to not only but mainly to identify Apps on your device that are “calling home” or establishing undesired connections. There is also a tutorial called Identify hidden App Communication.

  • Completely renewed HTTP Tool

So far, I was not quite happy with the HTTP Tool. On one hand, it was able to reveal a lot of Website internals but on the other hand it often failed to display websites correctly. This has been resolved now. The HTTP Tool was completely re-written and now feels much more like Safari but still allows to perform the parameter traversal and standard password tests.

  • Improved Traceroute

Traceroute now resolves addresses much more reliable and faster than before.

  • Improved Certificates Tool

The domain names that belongs to a certificate are now listed separately one after the other so you can now easily inspect (e.g. visit) each individual website the certificate belongs to. This is especially useful along with the Connections Tool as described in the tutorial.

  • Other bug fixes and improvements

Unfortunately, in the past, some features did not regard timeout values which caused the App to crash in some situations. Also, an iOS bug caused some Tools to crash when one of the Tool Buttons (e.g. in the FTP Tool) were hit while the keyboard was hidden. All that has been solved now as well as some other minor bugs and improvements as usual.

ALDI / MAGINON / Rollei WebCam findings – Update

This is indeed a scary story.

Today, I went to my favorite discount grocery Store (ALDI) for buying some items. To my surprise, they offered PTZ WiFi WebCams for less than 40EUR (about 45 bucks) so at the checkout I asked for a couple of those cameras.

Once back home, I did some quick researching and can’t believe what I found. The camera came with default credentials (guess what: admin as username and blank password) so I started using my NetworkToolbox to explore the HTTP-Head information of the Camera internal web server. The results were:

Content-Type: text/html
Server: mcdhttpd/1.0
Connection: close

This revealed a very ‘good’ string (mcdhttpd) to search for on Morpheus or Shodan with my NetworkToolbox. Quick searches confirmed that the ALDI Camera was in fact the renamed Rollei SafetyCam. (You will agree that this Camera uses a quite misleading name after read further. ALDI must have known the issues as they call it different 😉 )

Both, Morpheus and Shodan found hundreds of such cameras even around the world. Most of them in Germany, Austria, Hungary and Switzerland where ALDI is locaded and seemed to sell this WebCam. Of course, I didn’t try but I am pretty sure that there are lots of cameras using the same default credentials.

UPDATE: Thank you for your reports, confirming that several of those entries are indeed still using the default credentials.

Until now, you might think, “Ok, so I can look into somebody else’s Garden or nursery room or listen to what the say – so what?”

But it gets worse.

The funny WebCam offers WiFi and direct DynDNS support and so it also includes configuration pages for maintaining those credentials. The good thing is, the Camera supports WPA2 PSK AES and TKIP WiFi encryption, the worse is, the PSK Key will be displayed (and likely stored) in plain text. So once you find such a camera, you know how to access the WiFi network of the owner.

Even better, almost the same applies to the DDNS settings. Here, the Password is a secured text field, but the password can easily be read out. So by this, you even know how to connect to that WebCam (and the network!) in the future.

Can this get worse. Yes, it can:

The same security issues apply to the setting for the Mail that the device can send in case of alarms. Mailserver, mail username and password are plain-text or easy to be read out. So we all can be lucky to get more spam in the future, sent from those WebCam mail accounts. Thank you!

So what is my Point?

  • I complain that this camera uses default credentials. This is by all means NOT NECESSARY. There are many good alternatives. The simplest would be to request a password change along with the first login. And even if Maginon/Rollei would not be able to fix this security flaw, they should have a big warning in their manual saying “THE FIRST THING YOU SHOULD DO IS TO CHANGE THE DEFAULT PASSWORD“.
  • I complain (even though this is unfortunately common to many devices) that they respond with a unique, easy to identify string on a HTTP HEAD request (mcdhttpd). This fact alone is responsible that thousands of ALDI customers that are on risk now as their devices can easily be found.
  • I complain that they display the WiFi credentials in plain text and don’t encrypt other passwords (DDNS, SMTP Server, FTP, Additional users) so that they can easily be read out with a web browser. This is again simply NOT NECESSARY and INSECURE. I also bet they store them unencrypted (why to encrypt something that is displayed anyways)
I contacted Maginon, informed them about these security issues and asked for a statement but got no response yet.

Some screen shots in the Manual contains dates of the year 2012. Likely this was the year when the Camera was developed. Looks as the security standard is even older and it has never been updated.

Very likely, this piece of hardware contains more internal vulnerabilities and security issues.

This is again an example of how a single device can jeopardize your whole network security when added to your network.

Don’t trust the evil.

Have a great weekend.



Just to keep you updated.

I have just finished the work for the next Update of NetworkToolbox.

Besides some bug fixes (sorry for the bugs in the current version) and many other improvements, the new version contains two nice features.

First, I will introduce PKI (Private-Key-Infrastructure) features with the next version. This includes possibilities and explanations on how to generate encrypted Public and Private keys and to use them as a replacement for login username and passwords for a more secure SSH or SFTP access. I have also added a PKI Key manager which can be used to generate, import and store keys which can be used from inside the SSH or SFTP tools.

Second, I added an interesting feature that shows all current connections to and from your device. This is quite useful if you want to identify other Apps on your device which calls home or opens hidden advertisements to make money. Such connections will be displayed in the new tool.

Normally and as already mentioned in other blog posts, I use a network sniffer on my Linux computer to find undesired network connections from Apps that are installed on my device. This was quite time consuming and complicated.

By the new connections tool of NetworkToolbox, I was already able to identify a couple of new bad connections within a few seconds. It was even helpful that I was able to combine this with other built-in tools such as the certificate tool which helped me to quickly identify each connection as either normal (like Apple or mail connections) or undesirable sites like appsflyer.com or pushwoosh.com which ended up quickly on my firewall.

Just two examples of what is coming next.

I can’t wait to release this update to you.

So please stay tuned and … don’t trust the evil!



You better remove PHP FileManager

If you are running a website and are using PHP FileManager you can be quite certain that your webserver has been compromised. The reason is, PHP FileManager, sold from Revivedwire, has a backdoor since 2010 along with several other critical security vulnerabilities. Revivedwire has been informed long time ago but since recently still sold PHP FileManager along with the Backdoor and vulnerabilities. Can that be right?

I said “quite certain” because PHP FileManager installations can easily be found using Google (you even don’t need Morpheus or Shodan). As already disclosed,the backdoor username is simply ****__DO_NOT_REMOVE_THIS_ENTRY__**** and the md5 hash for this username is da26c70fc120d803e24bff0c5e5f6bdd. A quick Google search for this hash reveals that the equivalent password for this hash is travan44 .

Using these credentials, additional users can be created with full admin rights, files can be uploaded and executed remotely so one can not only download sensitive files but also get full access to a webserver within seconds.

There are ways to remove this backdoor from an existing installation but because PHP FileManager contains so many additional critical and easy to use security vulnerabilities, the only recommendation I can give is to completely get rid of it.

Don’t trust the evil!



P.S. I am already working on the next version so stay tuned.

Again about Piwik

I thought this update deserves a separate post so here is the latest update to “Scary piwik findings“.

It seems my post regarding Piwik caused a lot of rumors and discussions.

Piwik contacted me yesterday with the following mail:

…Unfortunately, not all of the points mentioned are correct and we kindly ask you to issue a public correction, especially because your blog is a valued source of knowledge for many IT professionals. Below we present a short clarification of the two points raised in your article.

Firstly, all Piwik users have the possibility to make their analytics report data publicly accessible by anyone, but this is by no means a default setting. By default, all reports are protected and nobody can view the collected and analysed data without first signing in with a valid user account. It is, however, possible to make reports available to anyone – this feature was developed on purpose and is well-documented in Piwik’s FAQ. Some organisations, such as the Pirate Party mentioned in your publication, decide to make their analytics data open to anyone on purpose. This is mainly because their Piwik data may be of use to their communities.

Secondly, it’s true that some of the Piwik servers’ URLs can be discovered in search engines using allinurl: “piwik/index.php”. We would like to emphasise that this poses no security risk as Piwik, by default, protects all user data behind a login screen and there is no possibility of a data leak. Furthermore, an improvement will be developed by our community to tackle this issue (details: https://github.com/piwik/piwik/issues/6552)

And here is what I responded:

many thanks for your mail. I mainly agree to almost everything but not with all you wrote.

First of all, let me assure you that it was also not my intention to blame Piwik as I found it to be one of the (if not the) best statistics tools available, especially due to it’s possibility to generate stats without storing IP address information – as already mentioned in my blog.

I am usually referring to Piwik as “the opposite to Google Analytics” which I hope is a compliment.

I am aware and can confirm that the default settings of Piwik don’t allow unauthorized access to the stats per se.

However, my findings did indeed reveal security issues along with Piwik installations as follows:

When using these inurl: queries, you will find a lot of half-done or broken Piwik installations. The diagnostic messages that can be found are very helpful for the webmaster to fix the Piwik installation issues. However it is also very helpful for hackers as these diagnostic messages reveal the physical server directory structures, database names and I even saw DB user names entered by the webmaster. One example, why this is dangerous is the recent ProFTPD exploit for which a hacker will just need to know the physical directory structure in order to copy files to other location which can either be accessed from outside or files that contain information that, once overwritten, will no longer protect files or directories.

Second, even if the default settings of Piwik don’t allow anonymous access, it is scary to see so many installations where it is indeed possible. In most cases it is quite obvious that those installations are not intended to be open for the public and as mentioned in my blog, even if anonymous access has not been configured, in some cases it was possible to download the stats via the Piwik API. This at least sounds as there are webmasters who have issues with a correct configuration of Piwik.

Finally, the huge amount of wrong, mis-configured and unintentionally open Piwik installations surprises me. I can’t remember similar findings in similar cases like some years ago with phpBB.

Regarding the Pirate Party, they seem to have a communication issue as they are talking about different Piwik installations and they claim they are using Piwik since May 18. 2015 but their Stats start in 2011 and they forgot (still!) to update their disclaimers on the two mentioned websites. But that’s no security issue and not really worth to follow up. Just for clarification.

My suggestions to you are as follows:

  • It seems some Piwik installations used to be ok some time ago but for some reasons (maybe changes/updates on a server) seem to get broken. In such situations, I would suggest to not reveal server information on the Piwik Admin website.
  • In general, I would rather suggest storing such information in log-files instead of displaying them so that they can only be accessed with appropriate privileges.
  • I would suggest to split/separate the API URL from the Admisistration and Statistics URL. That would also support the use of .htaccess protection to the Admin and/or Statistics part of Piwik.
  • I would definitely recommend to add the noindex, nofollow metatags as mentioned in your blog but I would also suggest to place an initial robots.txt file on the webserver root if it doesn’t exist or add lines to it if it exists. Both at least hides Piwik from search engines (even though not all engines regard those but Google does and was the main source of my findings)
  • If one or all of the above would be too difficult or not yet possible, at least place some big warnings in your setup documentation or setup UI (like you already do for other purposes)

I really appreciate your efforts to improve security and privacy in Piwik.

This helps to create a better, more secure world.

Thanks again,

best regards,


Why is McAffee, Avast, Symantec free ? They collect and sell your data! (updated)

Did you ever wonder why companies like Oracle or Adobe always wants to install unwanted software such as McAffee along with their free Java or Acrobat Reader ?

Or why so called “Best Antivirus Software” such as Avast or Symantec comes for free from your provider or pre-installed on your PC ?

Are those companies so generous? Do they only want your best?

You guessed it : No, of course not. They want money. Not just your money.

They get paid for every single installation of this unwanted piece of software!

So why is that ?

Because the unwanted software gets paid because it collects your data and they sell it.

Ok, you don’t believe me right ?

So here is an example:

Avast recently confirmed that they collect your data while running on your PC and scanning for viruses (see here if you don’t believe me)

Jumpshot is selling your data for just as much as US$ 500 per month! per account (see their pricing on www.jumpshot.com)

Avast claims that they don’t make money out of that but do you believe this ?

Do you believe McAffee, Ask with their Ask Toolbox and others don’t make money with collecting your data?

I personally don’t.


It’s a funny coincident that Tim Cook yesterday talked about the very same subject. His speech at the Electronic Privacy Information Center (EPIC) is really worth reading and most of what he said speaks my mind. You can find his speech on the verge .

He said for instance:

“You might like these so-called free services, but we don’t think they’re worth having your email or your search history or now even your family photos data-mined and sold off for God knows what advertising purpose,” … “And we think someday, customers will see this for what it is.”

Don’t trust the evil!



Scary piwik findings – Update 3

Maybe not all of you know what Piwik is. It is very nice tool for website statistics. I like this tool especially because it offers features to hide and even don’t record visitors IP addresses and private information but still generates nice and good website statistics. So I would call it basically the opposite of Google Analytics.

Since Piwik is getting increasingly popular, many websites started using Piwik but like so often, even Piwik requires some basic understanding of PHP, Linux and Server security. Some website Admins seem to be blinded by the easy user interface and assume it is as easy to configure.

Obviously that’s not the case. There are several open (and more worse: half-done) Piwik Installations out there which can be accessed by anyone easily. Such installations are quite dangerous for the webadmin because they reveal a lot of important insight information about the server configuration and it will not take much to use such an installation to hijack a complete server.

You may wonder how such servers can be found. This is also quite easy and in that case Google is our friend (in other cases I would reject this statement vehemently). As mentioned some posts before, Google can be used to search for URLs with specific parameters if you prefix your search term with


so in case of Piwik you can enter

allinurl: "piwik/index.php"

Which will give you a list of websites where piwik is installed. It is funny alone to browse through these findings which often contains error backtraces and error logs.

I was even (not) more surprised that some installations even allowed anonymous access with admin privileges. To check for this, one just needs to add either either this:


or this


to the Google result list url right after


So for instance




There seems to be an issue with Piwik that it is possible to download statistics even if there is no view access. If you add


You will get a nice Excel or CSV file with the website details of Site=1 (change to any other number for additional websites).


I did contact the German “Piraten Partei” before I wrote this blog post. So far: no answer. Meanwhile they responded to the press that they intentionally left the Statistics open to the public. This is fair enough as there is nothing to hide.

However, two questions remain:

  1. why don’t they tell us that they are collecting our information (especially search queries, website referrals and exit sites) ? In their website disclaimer (even on Andrea Bogners website) they say “Eine Speicherung von Verbindungsdaten … erfolgt nicht” which means “we don’t store connection data” which is obviously wrong.
  2. If they intentionally left their Piwik stats accessible, why don’t they officially link to these stats. Is there just an elitist circle who had or has access to these stats ?


Please read this separate post for a further update.

Best Regards,


Warning when using ProFTPD

This is a security alert, if you are running an FTP server that is using ProFTPD and are using the mod_copy setting.

A serious security issue was found in ProFTPD which allows copying of files such as /etc/passwd or wp-config.php even without authentication. This is a serious issue. Some Servers have already been reported as compromised.

This Vulnerability has been assigned the code CVE-2015-3306.

To check if your FTP Server is vulnerable, I have just added a new Security Check module called “ProFTPD mod_copy exploit (CVE-2015-3306)“.

Just perform a Data Update from the Settings Screen and perform a Data update. After the Update you can select that new test in the Security Check Tool. To run the test, you need to enter the IP address of the server you like to check. The port can be left blank and is optional.

If your server is vulnerable you should either remove the line

LoadModule mod_copy.c



or completely stop the ProFTPD service on your server. As per today, there is only a quick patch available for ProFTPD which requires to compile ProFTPD on your server. I would not recommend to use FTP anyway. Instead use SSH/SFTP.

Don’t trust the evil!

Good luck!


New version 8 of NetworkToolbox available

Finally, Version 8.1.3 of NetworkToolbox has been released by Apple.

Below is a summary of changes to the previous version. This is quite a long list. There are three new tools (27 in total now) and several parts have been completely re-coded. But this time, once I finished implementing one feature, I can’t wait to implement the next on my list. Maybe next time, I will create smaller updates.

Please support my work on this app by writing an app review. This really keeps this app going so you will also benefit.

If you already wrote an app review, you need to update it as otherwise it will get lost as every review only applies to a certain version.

Many thanks!

List of changes:

■ New Network and Port Scan engines

Network and Port Scanning is now blazing fast and even more accurate than before.

Now, hundreds of addresses and ports will be scanned simultaneously as fast as possible but still with the best possible accuracy. Since scanning is now way faster, all scans are repeated automatically a few times.

Scanning is also now random so that Firewalls and Intrusion detection systems will not immediately identify each scan easily.

■ Bookmarks is now Logbook

A new Logbook functionality has been introduced and the formerly available Bookmarks functionality has been integrated in this new Logbook function.
Logbooks can collect the following type of information

  • Schodan and Morpheus Scan results
  • Network Scan results
  • Port Scan results
  • Links
  • Hosts (= former Bookmarks)

Best of all, Network- and Port- scans can now be compared to each other. This way, you can quickly find out what has been changed in your network between two scans.

Logs can of course also be exported or printed.

■ Custom Device Names

You can now (optionally) assign individual names for your devices on your network. This makes it easier than ever to identify each particular device in the various scans.

These names are tied together with the MAC address. Such a maintained device name will be displayed instead of the network name in a different color.
Custom Device Names can be maintained in three different ways

  • In the Network Scan results. Just open the details of an entry and here you can directly enter an individual name
  • You can export a complete list of a network scan to the list of individual names
  • You can maintain the complete list of individual names from inside the settings screen

■ Improved DNS tool

The DNS Tool has been improved in several ways.

It still provides information about a certain domain with its IP Address, Provider, country and location.

Now, this tool also performs a reverse-DNS lookup with more than one record, if available.
Second, it now provides DNS Server information such as MX, NS, SOA and TXT Records.

■ Devices tool improvements

Now, all available interfaces (not just WiFi, Cell) will be displayed with much more detailed information. This way, you can even investigate your virtual VPN devices.

Proxy information now is also included.

Sensors such as Gyroscope, Accelerometer etc. will now be displayed graphically.

■ HTTP browser

The http tool now contains an improved browser. The browser also now records all requests a website initiate (even requests initiated by scripts) so you can easily inspect scriptfiles, images that are being loaded or even the sources of Ad banners.

The password test also has been improved and can now fill out many more types for login forms.

■ New Security Check tool

This is another new tool which required most of the development time. This tool contains several individual security checks for various exploits or issues. So far, it contains only a few checks but there are more to come over time.

The challenge was to implement a tool that I can use to quickly provide certain tests to you, without the necessity to send out a new app update. This is now possible with this new Security Check tool.
The idea was born when I added the Verizon Supercookie test but that was a quite simple test. Now even more sophisticated tests are possible and I can add all those tests via Data updates.

To use the test, you can either select the test inside the tool from the list or, like with most other tools, when working on results of any tool and using the […] button
I will announce new tests in the news section of the app but not on my website as this is too closely related to this app.

■ New Web-Service Tool

This new Tool allows to explore or debug SOAP and REST Web-Services. All API parameters such as URL Parameters, Header information and Request Body can easily be maintained and even stored under an individual name. The API requests can be executed via a HTTP-GET, -PUT or -POST methods.
JSON and XML results are being displayed in a hierarchical tree browser.

There are a few predefined Web-Service samples included such as the Google Geo API.

■ New Mail Server Tool

This tool checks for POP3, IMAP and SMTP mail services and provides useful information either for your Mail-Client settings and possible improvements for the Mail-Server settings.

■ Resources section has been completely re-coded

The resources section of the app contains a lot of information but wasn’t easy to find and use. It now has a similar user interface like the main app screen. It now also allows me to add more information via Data updates.

■ Various other changes and bug fixes

  • Several design changes throughout the whole app
  • The MAC address bug has been fixed which showed a wrong last byte of the MAC
  • The local IP address has not always been displayed correctly (e.g. was shown as “error”)
  • The MAC address is now displayed in the Network Scan report and no longer only in the details screen
  • IP Calculator improvements
  • Improvements for iPhone 6 and 6+
  • 64-Bit support
  • iOS 8.3 support

Please don’t forget to check for a data-update after the installation.

Please let me know should you find a bug or if you have additional ideas or requests.

Kind regards,


WiFi scanning

I received quite a few questions regarding the possibility to add WiFi scanning to NetworkToolbox that displays the SSID (WiFi name) and RSSI (signal strength) of WiFi networks around you.

Unfortunately (or I would call it fortunately) Apple removed the possibility for developers to access the WiFi network device from inside an app (at least for non-Apple apps).

For this reason, there is no app available on the AppStore that can do these kind of things. There used to be a few apps in the past which were able to provide this on a very limited basis but they don’t run anymore on iOS 8 and can’t be updated by the developer as it would then not pass the App Store review process. Such apps have been submitted to Apple by the time when it was still possible to access the network device.

However, what a “regular” developer can’t do seem to be possible by apps developed by Apple.

See how you can still scan WiFi networks

There is still a way to scan your WiFi network although it’s a bit tricky to enable it.

The solution is, to use Apples AirPort Utility app and to enable a hidden feature for it. This works, even if you don’t have an Apple WiFi router.

Here is, how to enable WiFi Scanning:

  1. Install the Apple AirPort Utility app from the App Store
  2. Start the app one time and then close it
  3. Go to Settings (of your iPhone/iPad) on the main screen, scroll down until you see the AirPort app and select it
  4. Enable “Wi-Fi-Sanning”
  5. Start the AirPort Utility app again
  6. Tap on “Wi-Fi Scan”
  7. Tap on “Scan”


After a while, you can see all WiFi networks around you even with Channel information, BSSID (Mac address of the device) and RSSI (signal strength). If you tap on an entry you can even see the more information like the signal strength history.

I think that’s a not-too-bad workaround.

Stay tuned!

Best regards,


Victory against Verizon for violating privacy

Maybe you remember my post Verizon spies you out.

Today, Verizon gave up and decided to allow the customers to opt out of its UIDH Supercookie tracking program (see hold Verizon accountable for violating its users privacy for details).

So this is a victory against Verizon and now you may want check here: Verizon to learn how to opt out. But you may also want to check here: CPNI just in case you also want to opt out for Verizons CPNI.

This sounds like good news but why does every single user has to take action ? This is incredible and an ignorance of the customers expectations of privacy. If you read my post you know why.

“Verizion Test” in NetworkToolbox still available

At this point, I would like to remind you on the Verizon test I added to my app NetworkToolbox so you can check yourself if your iPhone or iPad still submits the UIDH. You can even check if you are not a Verizon customer.

Verizion is lying

Furthermore, Verizon is still lying. Yes, there is no other word which would adequately describe their following statement on the aforementioned website:

It is important to note that the UIDH is a temporary, anonymous identifier included with unencrypted web traffic. We change the UIDH on a regular basis to protect the privacy of our customers. We do not use the UIDH to collect web browsing information and it does not broadcast individuals’ web browsing activity out to advertisers or others.Verizon wrote

This is rubbish! See why:

Some users were so kind to send me their results of the Verizon Test of my NetworkToolbox app so I was able to find out the following (some information have been X-ed out here of course):

One user reported the following at one day:


And a few weeks later this:


So the IP address was different but the UIDH the same.

Another user reported this:

IP: 70.210.131.XXX  UIDH: XXX3NDI5Njg2NQCCGgKg3Pg0AeRF49zrPVGQJ6mMku1+YV1PbkqWhmUNKw==

And just two days later this:

IP: 70.210.132.XXX  UIDH: XXX3NDI5Njg2NQCTU6e+AvPSyJUuozY84f5P/wH856jPnSIDHuYAIJYbSw==

So here, the IP address obviously changes but also the UIDH did change.

Verizon said the UIDH is encrypted. Really ? Not really!

The UIDH is simply BAS64 encoded which is just another way of representing and packing a number. I wouldn’t really call it encrypted. So I BASE64-decoded both different UIDHs and voila: Both UIDHs contain one and the same number XXX4296865.

So is Verizon lying? Yes! The outcome of my investigation reveals that the UIDH is NOT temporary, not encrypted and in fact DOES broadcast individuals’ web browsing activity out to advertisers.

It is even easy to use by all websites not just of those of Verizon’s advertising customers.

In fact, Verizon is jeopardizing their customers privacy!

Don’t trust the evil!

Tired of ads? – Happy New Year!

Happy New Year to you!

I hope you all had a good and secure start in the new year.

As so often, things you almost forgot and believed to be solved forever might come back after a new year break in a new incarnation and reminds you that there is no such thing like the “ultimate solution”. However, let’s see it as a challenge to at least get closer to the “ultimate solution”.

In this case, I am talking about ads which – all of a sudden – reappeared on my iPad, PCs and Macs even though I (at least thought) found a good solution by (ab)using my routers blacklist (see my flurry post from last year.).

So what happened ? After a bit of investigation, I found that some ad’s have changed from http:// to https://. This for me looked a bit surprising as ads usually (should) have nothing to hide so there should be no need to encrypt the web communication especially because of the extra effort for the ad-server to maintain certificates etc..

By that time, I was under the assumption that https:// addresses will be filtered by my router blacklist in the same way a normal http:// connection is. Not just because https just means that the content is transfered over port 443 instead of port 80 and even if traffic uses port 443 and is SSL/TLS encrypted, the domain needs to be resolved and if it’s blocked it can’t be resolved.

But further tests showed that my router indeed is just filtering http domains and not https. How come ? Further researches led me to the finding that (at least in the investigated cases) the issue was caused by websites which are also using https that include add banners with another https address. In such a case, the data (content) of the original website is SSL/TLS encrypted and maybe that’s why the containing https link is not filtered. I also found that my favorite AVM router is not the only one not being able to block https domains. Many other also can’t and even some popular firewalls have the same limitation.

I really don’t like ads do you? I am tired of ads!

I really got used to the ad-free websites and apps and I was also quite happy not to rely on such dubious Ad blockers like AdBlock Plus which even doesn’t really help to get rid of ads on my iOS devices. So I started thinking of a better solution. Especially because the router solution I was using so far only works with a few routers.

openDNS an alternative ? not really!

One solution I tried was openDNS . openDNS is a service on the web which offers two IP addresses that can be entered as DNS servers in your router. So openDNS replaces the DNS server of your ISP. All DNS queries will be sent to openDNS and they respond based on filter rules with the correct IP address or a dummy address. The good news is: it’s working. The bad news are, it costs about $20 per year (as the free service doesn’t offer enough custom filter settings) and much extra effort is necessary to handle dynamic IP address changes if you (as I) run your own DynDNS solution. They offer a in combination with their own service dnsomatic.com which can be used to chain additional DynDNS services but that doesn’t seem to work quite well. Finally (as I don’t trust the evil as you know) it is quite clear that they are collecting my DNS requests and sell it as this is quite interesting information for the ad industry.

So I discontinued my openDNS activities and thought about another solution.

running my own DNS Server!

And here is my (new) “ultimate solution” :

A Raspberry Pi connected to my favorite AVM router.

It was really simple to use an out-of-the-box $30 Raspberry Pi, setup my own “openDNS” by using dnsmasq on it. The Raspberry gets powered by the USB port of my router and is connected to it with a short network cable. No additional configuration on the clients was necessary and I just had to enter the Raspberry Pis IP address as DNS server address in the router settings.

My blacklist now resides on the Raspberry Pi and my router is no longer misused to blacklist ad servers.

even more advantages!

I now even have three more advantages:

  • HTTPS domains are also filtered. So no big ad at the top of the youtube.com site. Hurray!
  • DNS requests are noticeable faster as they are now cached inside my network
  • Optionally, I can easily monitor all the DNS requests of my whole network

The last advantage is very comfortable in order to find additional servers that want to be blocked, especially when using an iOS device. In the past I always had to setup a proxy for this.

So I am happy again!

If you are interested in this solution, please drop me a line (or maybe additionally leave an app review which I would greatly appreciate;-) ) and if there is enough demand, I will create a small installation summary and post it on my website. I can even share my blacklist if you are interested.

Again, have a good, secure (and ad-free) start into 2015!

…and don’t trust the evil!

Best regards,

Beware of using eCards – instead have a Merry Christmas

Most of you may view eCards as harmless ways to spread Christmas cheer. You may think they are convenient or fast and easy and there’s no hassle queuing up at the post office and trying to beat the Christmas postal deadlines.

But most of them are anything but harmless. At least I don’t know a single service I would recommend.

eCard providers are well known as Email collectors. They sell the Email addresses you entered and even analyze the message you select or added to your seasonal greetings. They usually send a tracking code along with the mail and claim this is to generate a receipt for the sender but in addition, they keep the receivers IP address and will know where exactly he lives.

Last year, some even distributed viruses along with their greeting mail.

If you like to do yourself and especially your friends and loved ones a favor, don’t use eCards. Instead, write a regular letter or just call them (of course don’t Skype them).

And if you receive an eCard via Email, you better delete it. Maybe send the originator a link to this post and call him or her.

Don’t trust anything which is for free – don’t trust the evil.

New data update

Today, I sent out another data update with a new MAC Database and some other changes (Thanks Martin and Mike for your hints and help!).

A new app update is already under development which will cover a lot of suggestions and will offer some new features. I will need some more time to get it completed and tested but early next year I expect to be able to send it to Apple.

I really appreciate all your support and suggestions. Please continue to write if you have questions, suggestions or even find bugs (thanks Emile).

To you and your families, have a Merry Christmas and all the best for 2015!

And don’t forget: don’t trust the evil.

Best regards,

Your 10 Year Google History

Just a quick one:

Are you a google member (even because of YouTube or gmail) ? If so, login to your google account and select:


Then, head to “Things you search for”.

Isn’t it interesting to see what you searched for even 10 years ago. I believe Google also agrees.

If you don’t agree, you can delete all entries here and select “Pause” on the previous screen.

The same applies to “Places you have been”, “YouTube searches” and “Things you have watched on YouTube”.

Even here, you can delete and pause everything.

But no worries, be assured that Google will keep a backup – just in case.

By the way, Amazon does the same with all your purchases and all Items you ever searched for.

Don’t trust the evil.

UPDATE: Verizon spies you out! – Verizon test added to NetworkToolbox

Verizon spies out their customers and creates behavioral profiles by deep packet inspection. They then even sell your data to make even more money.

You don’t believe me? Read further and finally check for yourself by using my recently added test to NetworkToolbox.

What Verizon does is that they insert some data to every network stream that goes from your device through their Wireless Cell/G3/4G/LTE network whenever you access any website. They are adding a special X-UIDH header that works like a supercookie. Any website can easily track a user, regardless of cookie blocking and other privacy protections. There is even no relationship with Verizon required.

This supercookie acts like a super UUID which uniquely identifies you to the website. Any website can track your visits and re-visits and linked websites can even track your visits to different websites.

But even worse: Verizon sells your identity to websites and closes the link between you as an anonymous visitor of a website and your real personality. It is unknown yet to what extend Verizon sells your personal information but they do and they are making lots of money with it. They call it “PrecisionID”.

Apple was blamed about the existence of the unique device ID and recently they even removed the MAC Address (as you, as a NetworkToolbox user will know). But such IDs can never be as dangerous as a unique ID inserted by your provider to any network stream between you and a website.


After hearing about that, I quickly created a scan for this type of information. To run this test, just perform a data update in your NetworkToolbox (if you don’t already did). Then, head to the “Security Check” Icon and select “Verizon Supercookie Test“.

Verizon offers the following website to switch off this supercookie:

https://www.vzw.com/myprivacy (This link needs to be copied and opened in Safari. Read below “funny side-storry” why)

I strongly suggest to use that service and once Verizon claims they switched it off, use the test to double-check if they really did.

Even if you are not a Verizon customer, just run this test and see if there is anything else your provider adds to your data stream. If so, please let contact me. Maybe we can reveal another spying provider. Would be interesting.

Funny side-story: If you visit the aforementioned link of Verizon, you will visit a website with a wrong certificate. Normally you should never bypass such a warning of your browser (even though not all browsers will generate a warning). You can use NetworkToolbox to see what’s going on here. Just use the “Certificates” tool of NetworkToolbox and enter www.vzw.com and port 443 (which is HTTPS). Now in the first line you can see where the issue is. It says “verizonwireless.com” but must say vzw.com. This is, why you get the warning.

So much to their technical expertise. Do you still trust them? I don’t.

Don’t trust the evil!

P.S. I am receiving a lot of mails from users per day. Some of you have new ideas but mostly questions. That’s fine and I really appreciate any mail. Please be patient if you don’t receive an immediate answer. I will either be busy on app improvements (like these days) or with answering mails.

However, based on the amount of mails, I assume there are a lot of people using my app even on a daily basis. On the other hand, there are just a few app reviews yet. If you are unhappy with my app, please let me know. My goal is to keep (or make) NetworkToolbox the best Network utility on the AppStore.

If you are happy, please write an app review (there is a button for that inside the app). App reviews are so important for app developers. Think about yourself: when will you purchase an app ? Yes, when there are many reviews saying that this app is great.

Thank you!

Do you know flurry? It spies you out!

If you hear about “flurry” and think of a sort of ice cream, you are wrong, the opposite might describe it much better.

I recently started again analyzing the traffic that is passed between the Internet and some well-known apps we may use on a daily basis. Unfortunately, such analysis is not possible with my app NetworkToolbox as Apple restricts raw-socket access so I had to use my Linux PC for this.

The situation is still quite scary. Many apps are sending detailed information about your app usage, device and personal information to third party companies. This is not new but seems to get even worse. Yelp for instance uses three services in total such as adjust.io (see www.adjust.com), sb.scorecardsearch.com (see scorecardresearch.com), settings.crashlytics.com (see crashlytics.com) and of course google analytics. Other well-known candidates are graph.facebook.com.

The worst thing I have seen was however flurry.com (see www.flurry.com). Apps using the flurry service connect to data.flurry.com and loads of information regarding my device type, name, several IDs, app usage, settings etc. will be submitted to flurry. Even worse, most apps even don’t even encrypt this information when it’s being sent.

This screwball data collection nightmare even slows down the apps and uses up my bandwidth.

This is ridiculous!

You may think, what can we do against this ?

There is a quite simple solution at least for your home network so when you are connected via WiFi from your device.

The solution is to use the child protection mechanism of your router, if available.

In my favorite AVM Fritz router, I can maintain a blacklist of websites or IP addresses that should not be available from inside my network. This is basically to prevent kids from visiting certain websites. However, this also works perfectly to protect against these evil flurry scammers. Most routers have a similar blacklist available. Sometimes it’s quite hidden and cumbersome to maintain and enable but it’s worth to spent some time in this research.

So just add data.flurry.com (or even flurry.com) to that blacklist and you are fine.

You can also add the following for some of the other scammers:


and you may also want to consider:


and if you finally want to get rid of most of the adware even in apps, just add:


So once this is done, you will even experience that some of your apps will run faster, as some of those scammers didn’t even invest in fast servers. Flurry has a extreme high latency, at least in Europe and it even takes quite some time to submit all the device information and app usage to flurry.

(By the way, did you name your device something like “Mike’s iPhone”. Don’t do that otherwise they will even know your name).

As always, don’t trust the evil.

Best regards,

P.S. if you are interested reading more articles, just head to my website networktoolbox.de/news. The app only shows the last fifteen articles due to traffic reason.

Shellshock – update #2: Yahoo and winzip.com hacked

(see updates at the end of this article)

You may have heard already about the newest security issue Shelshock which already claims to be the worst ever computer bug. I partly agree to that statement.

In short: Shellshock is a bug of a program called “bash”, which is installed on non-Windows systems such as Linux and even Mac computers. The bug allows hackers to send commands to a computer without having admin status, letting them install malicious software within systems.

We all can be affected in two ways by Shellshock:

1.) If you run a computer/server (or device) that can be accessed from outside

2.) If you access a website on a server that has already been compromised

Regarding 2.) there are already servers, known for being compromised by malware which has been installed by using the Shelshock bug. Without being too pessimistic, I think it is not unlikely that will see soon such malware that captures sensitive user information on website visitors or access databases with sensitive information. This is possible as the malware, injected by Shelshock has full system access. Let’s hope that admins of those website will update their systems quick and carefully watch their server log-files.

Regarding 1.) If you run a linux computer your own (all Mac users do) or run a webserver with linux you may be affected if the bash version on that machine has not been updated recently.
You can test for the issue by entering the following command:

env x='() { :;}; echo vulnerable' bash -c "echo no problem"

If you see two warning messages and the message “no problem” you are safe. If you see vulnerable you are in trouble if this system is accessible from the internet.
Depending on your linux distribution, you should update your system by “yum update bash” or “apt-get update” followed by “apt-get upgrade” or possibly other package managers you are using.
All current Mac computers are also affected. Yet, there is no update from Apple but updating bash (and sh) is not too complicated. A good explanation can be found here:


Thus, securing your own systems is quite easy and you should hurry to do so.

However, what about all the devices, running linux like routers etc. ? “bash” is a quite heavyweight software which is not ideal for small devices. For instance OpenWRT/DD-WRT doesn’t use it. However, some routers and other devices such as streaming clients have bash installed and definitely need to be updated in order to get secured against Shellshock.

From my personal experience, I expect several new vulnerables and attacks for such devices in the near future. So you better should check for updates on all your devices.

UPDATE #1: Several of my webservers are already under attack, mainly from China. The biggest server is which currently searches for insecure servers and executes a script from I would strongly recommend to any webmaster to scan their logfiles for strings like ‘:;}’.

UPDATE #2: Yahoo and winzip.com were not as quick as us. They have been hacked already. If you have a yahoo.com account or are registered at winzip.com I urge you to change your passwords. Don’t wait. You will find more information here: www.futuresouth.us/yahoo_hacked.html.

Don’t trust the evil



Anatomy of a scam attack

Today, I received again one of those scam mails which informed me about an issue with my PayPal account and asked me to re-enter my account details.

You all know about these funny mails. It is still interesting that people still fall into this trap. Anyway, I trust you do what I usually do: Just delete such mails.

However, this time I spent some time analyzing this scam a bit:

1.) Mail header

By looking into the source of the mail. I found this:

Received: from unknown (HELO mx.elko.ro) (

This means, the mail was sent from a server called elko.ro. By visiting the elko.ro website, I found that this is a regular computer company. Most likely, their mail server is insecure and allows relaying and so, the scammers did misuse their server to submit this mail. But that’s not really surprising and helpful. Maybe somebody should inform elko.ro about this issue on their server.

2.) Mail attachment

As most of these type of scam mails, this mail also contained an attachment. This time just an HTML script which contains the form I should fill out in order to get my account re-activated.

By browsing through this script I found they did use some images and links directly from PayPal and some others from postimg.org. postimg.org can be used to upload images. Maybe somebody want to contact postimg.org and ask who uploaded the image 3wpnm7loj/STRADA.png for instance.

Anyway, the interesting part is, to whom the form will be sent after it’s filled out and here we are:

form class='safeSubmit multiplesubmitform' method='post' id='signup_form' name='signup_form' action='' onSubmit='return sTest();'

The form is being sent to Entering this IP address into the Domain Tool of NetworkToolbox reveals that this is a server in Russia, hosted by clodo.ru which is known as a very liberal web hoster.

3.) and so…

Nothing really. This was a real simple one. Even the script was coded badly and the text contains some dreadful spelling mistakes which makes it quite easy to identify this mail as scam. It should now even be easy to identify those guys but I doubt that somebody in Russia will care.

However, even though it would only help for this specific type of scam, I would recommend (again) to block direct IP access in your firewall / router (the parental controls offered by some routers are doing a great job for this) and you may want to block the address ranges of clodo.ru which is ( – because most likely, you won’t visit a website hosted at clodo.ru. Blocking direct IP access will redirect you to an error page of the firewall/router whenever a link will be opened that only contains an IP address rather than a fully qualified domain name. Yes, of course, those guys could have registered a domain name in addition but then, they would have left another trace and just recently, the ICANN has started an initiative which makes it harder to register a domain anonymously.

So… Don’t trust the evil!



Starting other Apps from Network toolbox and vice-versa by URL Scheme

With the latest release of NetworkToolbox I introduced the possibility to use external apps as well as the opposite to use NetworkToolbox from other apps.

Some people contacted me and asked, what the heck does this mean and what is the purpose.

1.) External apps for NetworkToolbox

You all know the nice and useful selection-list that appears for instance, if you hit the […] button on an entry of a result list (e.g. a Network scan or Morpheus search).

This list offers you to use any other Tool of NetworkToolbox on the selected entry in the list. For instance, you can run a port scan on each entry of a Network scan or you can open the Browser tool after the port scan reveals an open port 80 etc.

For your convenience, the list highlights all entries that would make sense for a selected entry and even scrolls to those entries. For instance, if you selected a port 80 address, the HTTP tools will be highlighted.

Besides the Copy, Bookmark and E-Mail options in this selection-list the other entries range from Domain Infos until Trace route.

You can extend this list further by adding external apps in the settings section of the app.

This is useful, for instance, if you want to use your favorite remote access app from within NetworkToolbox.

To understand, how external apps can be started, you need to understand the term URL Scheme. This is basically the first part of a web address such as http://. In this case, http:// is the URL Scheme of Safari on your device. Other apps must not but can provide their own URL Schemes which will start a particular app when it’s being called. For instance, most popular VNC viewers are using the URL Scheme vnc://. To try this out, just open safari and instead of http://bing.com just type vnc:// and see what happens. Maybe your VNC app will start. Of course, the URL Scheme and the parameters that need to be used after the URL Scheme highly depend on the app itself.

To learn how to integrate your favourite apps into NetworkToolbox, just open the “External Apps” section in the settings and press the (i) Info button.

2.) NetworkToolbox as external app

Also NetworkToolbox offers URL Schemes to other apps which is nettb://. You can use this to open and perform tests with almost any tool offered by NetworkToolbox (Further down you will find a list of parameters, offered by NetworkToolbox).

So how can this be useful ? I will give you an example:

If you want to perform certain tests on a regular basis let’s say a website crawl for a few websites let’s say to google.com, ign.com and amazon.com. For this, just open the built-in Notes app on your device and enter the following line by line:


Now, press done and re-open the note. You will see that those lines have been converted to links. Once you tap on a link, NetworkToolbox will be opened to perform a web crawl on the given website.

Of course, the same way you can call NetworkToolbox from any app that offers the possibility to call external apps by URL Schemes.

List of URL Scheme nettb:// parameters:


Greetings from Def Con 22 – Improve your router security

As I covered this subject quite a few times here, Craig Young had a few good suggestions to improve your router security:

  1. Don’t enable remote management over the Internet
  2. Don’t use the default IP ranges. Predictable addresses make attacks easier. Rather than, consider or something else which is not commonly used. This is a simple but effective technique for decreasing the likelihood of a successful attack.
  3. Don’t forget to log out after configuring the router. Not logging out can result in a situation where the web browser used to configure the router remains authenticated, which opens the door for attacks.
  4. Turn on AES backed on WPA2 encryption and turn WPS off. Regardless of the complexity of your WPA2 password, don’t forget to switch off WPS!
  5. Passwords matter: Default passwords are often the same for an entire product line or are generated from a common algorithm making a device easy prey for an attacker. It is imperative that you and other users change passwords rather than using defaults.
  6. Keep the router firmware up-to-date.

If you follow these six points, you are still on risk if your router vendor included some back-doors or ‘forgot’ to fix security issues with updates. However, it’s the minimum you should do yourself in order to increase your router security.

If you use Morpheus or Shodan from within my app, you will know that millions of users don’t.

Don’t trust the evil.

New release 7 available!

Fortunately, after several months of development, the new release 7 of NetworkToolbox is now available on the AppStore.

It took quite some time to implement all of my ideas and suggestions I had on my To-Do list but it’s now done.

I even used the opportunity and made the app already compatible to iOS 8 but the main intention of the new release was to improve the usability and add some cool new features.

See what’s new about NetworkToolbox release 7:

■ Improved user interface
The user interface has been improved significantly to increase the usability, convenience, and effectiveness of NetworkToolbox.
It is now even easier than before to switch from the scan results of one tool to another for further analysis.

New tools:
There are now 24 tools in total.

■ Bonjour
Bonjour, which is Apples zero configuration protocol, can now be scanned and analyzed by NetworkToolbox. You will be surprised how many devices talk Bonjour in your network.

■ Certificates
Another new tool can be used to analyse and display server certificates in a readable form. Such certificates will be used to secure websites such as banking sites. Recently, some certificate authorities have been compromised and issued insecure certificates e.g. even for google. NetworkToolbox can now reveal such certificates.

■ Bluetooth LE
As Apple recently introduced iBeacons in their stores which are basically Bluetooth LE (low energy) tokens, NetworkToolbox now offers a new tool that can be used to scan for and analyze such iBeacons or any other Bluetooth LE device easily.

■ More and better device information
The Device Information tool now provides much more information about your iPhone/iPad such as Cell, Cell-Carrier, Hardware, Memory, CPU, Sensor and sensitive device ID information.

■ External app integration
NetworkToolbox now integrates also with external apps. External apps like your favourite remote access app can now be used from inside NetworkToolbox and the other way around. NetworkToolbox can now be started from inside other apps e.g. even by safari.

■ Shodan improvements
Shodan’s new API has now been integrated and you can even use your own Shodan API key.

■ Socket / Telnet improvements
The Socket tool now supports sending of special characters like ^C, TAB etc. It also includes new settings for echo and line wrapping and can even show non-printable characters in HEX.

There are much more new features that can’t be listed here.

Please note: Don’t forget to install the latest data update.

For those changes, major parts of the app have been re-coded but even though the app has been tested by several beta testers and on many different devices and iOS versions, there may be some bugs left that have not been found.

As always, please let me know about any bug, change request or suggestion, ideally using the support button inside the app and I promise to fix any bug real quick.

Again, many thanks for your feedback.

Please don’t forget to rate the app or update your review. Unfortunately, with every update I sent out, your previous reviews disappear. But you just need to slightly update your previous review to let it appear again. Many thanks for this.

Kind regards,


New update 6.07.01 available

Among some minor changes “under the hood”, this update contains:

■ Again, improved Morpheus
The Morpheus search engine has been improved further and is now better integrated into the app.

■ Custom Port ranges for the Port scanner
It is now either possible to select individual port ranges for all HTTP Services, Mail Services or upper/lower ranges or even enter individual ranges for scanning manually.

■ Custom Password list
In addition to the built-in default password list, it is now possible to maintain and use a custom password list for the HTTP, Socket, FTP, SFTP Tools. This way, you can pre-enter the know credentials of your servers and devices if you like.

■ Collect discovered password
Once you discover a username/password combination, you can now even store your findings along with the host information for later reference in the custom password list. So now, there is no need to write it down anymore. An explanation of these new features can be found in the updates info (i) texts.

■ Reverse DNS lookup
The Domain tool now also supports revers DNS lookups. So for instance, if you just enter an IP address, this tool may also show the domain name if there is a domain name registered for that IP address.

PLEASE NOTE: This app update also requires the installation of the newest data update. So please also use the “Check for data update” button in the settings screen of the app. The installation order (app or data update) does not matter.

The next app update will be a new major version I am currently working on.

Please remember to write or update your app review. This keeps NetworkToolbox going.

Thank you and kind regards,