▁ ▂ ▄ U𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

🦑Windows security trips :

1) Safe Wi-Fi in your home. This may seem like an easy task to some, but insecure or simple passwords in your home are a major problem that you can face day in and day out. The defaults are a bad idea in any advanced community. So make sure you change the default settings or ask your local professional to help you with this. When this is done, make sure the invited expert does not know your WPA2 password, so cover your keyboard while you set it. Remember that you are only responsible for providing the password to those you choose to trust.

2) Consider a VPN. Once you implement a virtual private network (VPN), your work from home is likely to be much safer. Identity thieves and hackers are more likely to extract your identity from outgoing traffic, so filtering is a good idea. Do not connect your devices to a VPN, as this makes your settings vulnerable and easier to hack.

3) Keep your devices locked. Data is largely stolen and re-hashed via insecure devices that are used without any passwords or security software. Any security, such as passwords, fingerprints, templates, or graphical passes, reduces the risk of data disclosure. However, be careful with facial recognition software as you can likely run into problems in financial operating systems when your face is imprinted on the system. Remember, your devices know what you look like, so use fingerprints.

4) Protect your smart TVs and smartphones with additional software. They are the most insecure and can reveal your personal information. This approach is absolutely unacceptable. However, you cannot let others spy on you through their devices. Look out for sophisticated antivirus software that allows you to use browser extensions, smartphone apps, and security gateways for your IoT environment.

5) Enhance your knowledge. Explore as many options as you can of how the Internet of Things is attacked daily by hackers and identity thieves. Improve your information security competencies. Be aware of internet security and remember that your interconnected gadgets are your weakness. As machine learning (ML) and artificial intelligence (AI) become more advanced, consider them as your key weapons against cyber attacks.

@UndercodeTesting
▁ ▂ ▄ U𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

Exposure to the production by Samsung of a 600 million pixel sensor lens area covering 12% of the back of the phone.
#Technologies

December's Fastest DNS: Here are the ones to have right away.
#Updates

▁ ▂ ▄ U𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

🦑list 3 ransomware real decrytors :

https://www.nomoreransom.org/en/decryption-tools.html

https://www.softpedia.com/get/Antivirus/Removal-Tools/Trend-Micro-Ransomware-File-Decryptor.shtml

https://noransom.kaspersky.com/

https://www.avast.com/en-us/ransomware-decryption-tools

https://www.emsisoft.com/ransomware-decryption-tools/free-download

https://www.mcafee.com/enterprise/en-us/downloads/free-tools/ransomware-decryption.html

https://www.quickheal.com/free-ransomware-decryption-tool/

▁ ▂ ▄ U𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

WhatsApp: escape users for a particular cause, the latest option is here.
#Updates

▁ ▂ ▄ U𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

🦑Network hacking exercice:
This is a short introduction on methods that use neural networks in an offensive manner (bug hunting, shellcode obfuscation, etc.) and how to exploit neural networks found in the wild (information extraction, malware injection, backdooring, etc.).

0 - Last Layer Attack
1 - Backdooring
2 - Extracting Information
3 - Brute Forcing
4 - Neural Overflow
5 - Malware Injection
6 - Neural Obfuscation
7 - Bug Hunting
8 - GPU Attack

Download:
https://github.com/Kayzaks/HackingNeuralNetworks

▁ ▂ ▄ U𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

This is what causes the most issues with radiation and 2020 and oldest smartphones.
#Bugs #Analytiques

Exposure that 2020 Apple TV will be launched on December 8, equipped with A12Z chip.
#Leaks #Technologies

▁ ▂ ▄ U𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

A POC Windows crypto-ransomware (Academic)

Run in Background (or not)
Encrypt files using AES-256-CTR(Counter Mode) with random IV for each file.
Multithreaded.
RSA-4096 to secure the client/server communication.
Includes an Unlocker.
Optional TOR Proxy support.
Use an AES CTR Cypher with stream encryption to avoid load an entire file into memory.
Walk all drives by default.
Docker image for compilation.

🄸🄽🅂🅃🄰🄻🄻🄸🅂🄰🅃🄸🄾🄽 & 🅁🅄🄽 :

1) git clone github.com/mauri870/ransomware

2) cd ransomware
If you have Docker skip to the next section.

3) You need Go at least 1.11.2 with the $GOPATH/bin in your $PATH and $GOROOT pointing to your Go installation folder. For me:

export GOPATH=~/gopath
export PATH=$PATH:$GOPATH/bin
export GOROOT=/usr/local/go

4) Build the project require a lot of steps, like the RSA key generation, build three binaries, embed manifest files, so, let's leave make do your job:

make deps
make

5) You can build the server for windows with make -e GOOS=windows.

Docker

6) ./build-docker.sh make

▁ ▂ ▄ U𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

Vodafone: what promotions await us for the Christmas month?
#Updates

Internet Via Satellite: goodbye to 3G, 4G and 5G connections.
#Technologies

▁ ▂ ▄ U𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

🦑Catch bad SQL queries :
#Hacking

1) download https://github.com/burrito-brothers/shiba

2) Install in a Rails / ActiveRecord project using bundler. Note: this gem is not designed to be run on production. It should be required after minitest/rspec.

# Gemfile

3) gem 'shiba', :group => :test, :require => 'shiba/setup'
If your application lazy loads gems, you will to manually require it.

# config/environments/test.rb or test/test_helper.rb
require 'shiba/setup

4) To get started, try out shiba locally. To verify shiba is actually running, you can run your tests with SHIBA_DEBUG=true.

# Install
bundle

# Run some tests using to generate a SQL report
5) rake test:functional
rails test test/controllers/users_controller_test.rb
SHIBA_DEBUG=true ruby test/controllers/users_controller_test.rb

# 1 problematic query detected
# Report available at /tmp/shiba-explain.log-1550099512

▁ ▂ ▄ U𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

Kaspersky creates a smartphone modeled after himself on the OS.
#Updates

Whatsapp: the list of smartphones no longer compatible in 2021.
#Updates

▁ ▂ ▄ U𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

🦑HOW TO FIX A HACKED DRUPAL WEBSITE ??

Step 1: Make a forensic copy of the site
Once you are sure that you've been hacked you should stop everything and make a forensic copy of it. Some people prefer to literally yank the network cable and power cable from the server, though that obviously isn't always appropriate and doesn't work for all environments (cloud, anyone?). If you can, this forensic copy could be an operating system level snapshot of the server(s) involved. Otherwise, go for a copy of the database and files. Store one copy to media that can't be modified like a CD or DVD.

Step 2: Decide to keep, rollback, rebuild, or throw the site away.
"Keeping" a site requires you to spend a lot of time and effort reviewing it. You may decide, depending on the nature of the site, that it is perfectly acceptable to throw it away or rebuild it. Perhaps the needs of the site have shifted and you were planning to rebuild it already. Perhaps it was for an event that has come and gone and you can make a static copy or just delete it all. Even if you've decided to rebuild or delete a site you aren't done with this process, but at least you've cut out a lot of the work in remediation. You may not be able to make this decision or may change your mind based on investigation you do as part of remediation. Start the process by considering this question and it may help ease your life. If you know the specific date that your site was hacked, you may be able to rebuild the site easily simply by using an older database and file backup (you make those and keep them around, right?).

Sidebar: Documentation and learning
One of the first things you should do is open two scratch pads. One for documenting everything you've discovered and that you're doing NOW. If you notice an important detail proving how the attackers got in, add the source of the information and as much of that information as you can. The second document is for things you want to do to harden your site that you think of as you go through the process. You may realize a lot of things you can do to make it harder for attackers, but their not easy or critical enough to do right now. Save those valuable ideas for later.

Step 3: Who should you notify?
You should start deciding who you need to notify about the issue. If your site had users and you believe your site was completely taken over then private content like their email address, IP address and anything else private on the site is compromised. In some locations you are legally bound to inform people of this exposure (e.g. in the case of sites requiring HIPAA or PCI Compliance), if not also morally bound.

If you are not the owner of the site, you should consider which stakeholders to inform. Visitors of the site might have been exposed to malware. The owner should be involved in decision making.

Depending on the nature of the site and who you suspect attacked it, you may wish to notify one or more law enforcement groups. Many local law enforcement groups are poorly equipped for dealing with these kinds of issues. But perhaps they will be able to help or refer your case to another law enforcement group.

Step 4: Should you take the site offline?
Again, depending on the nature of the site you may wish to take it offline. If you suspect that it is actively being used to distribute malware, send spam, or as a pivot point for further attacks then taking it offline and installing a placeholder will at least prevent further damage.

Note that taking the site offline likely does tip the attackers that you are aware of their presence.

If you don't take the site offline at the webserver level:

Make sure you've got your forensic copy and then delete out all sessions.

If you suspect passwords have been changed, you can update them to new values using a query like this:

update users set pass = concat('ZZZ', sha(concat(pass, md5(rand()))));

Users will be able to use the password reset tool to change their password.