hacking: security in practice
Where does one place a bounty on decoding a proprietary communications protocol?

I got a pallet from an industrial auction of late 90's early 2000's robotic servomotors a few years ago. Half of them are brand new, the other half working pulls from decommissioned robots.

I'm compiling an open source project for using old industrial robots with ROS. I've designed some great servo amplifiers and server/pc interface cards and got it working with ABB and Panasonic hardware but can't decode all the data from the FANUC Alpha motor pulse coders. Google gives me nothing.

I gave up a year ago and every time I open the garage I have to look at it, sigh, and step around the pile. I'm willing to throw money at the problem at this point.

Where would I throw this money?

Please respect rule 2. I am not asking for your services and any comments/messages offering them will be screenshotted and sent to the subreddit moderators.

submitted by /u/-Mikee
[link] [comments]

___________________________
@hacking_Attack
@Hacking_Video

hacking: security in practice
Some websites are able to determine that your not actually in the us?

So I got this play store gift card and when I entered it on my phone it said it can only be claimed in the united states, so I changed my google billing adreeas to the us, but I still got that messagee, so I used a vpn and a new google acount, but I still got the message, so I got a windows vps that was hosted in the us and logged into my acount and tried to claim the gift card but I still got the error message, how is google play store able to determine that im not actually in the us???

submitted by /u/Agitated-Farmer-4082
[link] [comments]

___________________________
@hacking_Attack
@Hacking_Video

hacking: security in practice
Potential iCloud Hack/Scam

I'm not really sure if this is the right sub for this, so if it is not, and you could redirect me to the right one, that would be great. Anyways, I was just browsing through reddit on my phone, and clicked on a link for a picture in someone's comment. It brought me to an Apple iCloud page that was blank with a grey loading circle. It spun for around 2 seconds before it hit me that it could be a potential hack/scam. I instantly clicked closed that browser, and now I am here. I clicked on the reddit account that posted the comment, and it was a bot account, with like 4 karma. Basically what I'm asking here, is should I be worried, or was it just nothing? I closed out of the tab before anything loaded, but I'm thinking that nothing would have ever loaded, it was just to stall while it could potentially infiltrate my phone. Thanks for any help!

submitted by /u/Lil-Parabala
[link] [comments]

___________________________
@hacking_Attack
@Hacking_Video

Hacking on Medium
How To Pay And Buy Online Anonymously | SCOT UG

https://cdn-images-1.medium.com/max/1080/1*NJmAtbsjSg-D5borTqVW7A.png
Some factors people think of first are their personal data, like the names of credit cards they use and their biography. However, hackers…

Continue reading on Medium »

___________________________
@hacking_Attack
@Hacking_Video

Hacking on Medium
How to know the secrets of a website server?

https://cdn-images-1.medium.com/max/640/0*rHY2MHx1yZUK5ey-.jpg
A website presents itself as all its information is public. However, there’s is an ocean of useful data hidden which isn’t visible to the…

Continue reading on Medium »

___________________________
@hacking_Attack
@Hacking_Video

Hacking on Medium
Privilege Escalation with MySQL User Defined Functions

https://cdn-images-1.medium.com/max/2071/1*nc03GvmuYZL4brqx7nAsPw.jpeg
Extending MySQL functionality with UDFs — Banzai, Proving Grounds

Continue reading on R3d Buck3T »

___________________________
@hacking_Attack
@Hacking_Video

Hacking on Medium
CISA emite una advertencia sobre las amenazas cibernéticas dirigidas a los sistemas de agua y…

https://cdn-images-1.medium.com/max/1622/0*FMHygPRbmvKZXeoD
PUBLICADO EN 15 OCTUBRE, 2021POR EHACKING

Continue reading on Medium »

___________________________
@hacking_Attack
@Hacking_Video

Hacking on Medium
Más de 30 países se comprometen a luchar contra los ataques de ransomware en una reunión mundial…

https://cdn-images-1.medium.com/max/1611/0*34mwIliQWa_ptJDo
PUBLICADO EN 18 OCTUBRE, 2021 POR EHACKING

Continue reading on Medium »

___________________________
@hacking_Attack
@Hacking_Video

Inceptor - Template-Driven AV/EDR Evasion Framework
http://www.kitploit.com/2021/10/inceptor-template-driven-avedr-evasion.html

___________________________
@hacking_Attack
@Hacking_Video

Modern Penetration testing and Red Teaming often requires to bypass common AV/EDR appliances in order to execute code on a target. With time, defenses are becoming more complex and inherently more difficult to bypass consistently.Inceptor is a tool which can help to automate great part of this process, hopefully requiring no further effort.
Features
Inceptor is a template-based PE packer for Windows, designed to help penetration testers and red teamers (https://www.kitploit.com/search/label/Red%20Teamers) to bypass common AV and EDR solutions. Inceptor has been designed with a focus on usability, and to allow extensive user customisation.To have a good overview of what it was implemented and why, it might be useful to tak a look to the following resources:The path to code execution in the era of EDR, Next-Gen AVs, and AMSI (https://klezvirus.github.io/RedTeaming/AV_Evasion/CodeExeNewDotNet/)Inceptor - Bypass AV-EDR solutions combining well known techniques (https://github.com/klezVirus/inceptor/blob/main/slides/Inceptor%20-%20Bypass%20AV-EDR%20solutions%20combining%20well%20known%20techniques.pdf)
Shellcode Transformation/Loading
Inceptor is able to convert existing EXE/DLL into shellcode using various open-source converters:Donut (https://github.com/TheWover/donut): Donut is "The Converter". This tool is more like a piece of art by TheWover (https://twitter.com/TheRealWover), and can be used to transform Native binaries, DLL, and .Net binaries into position independent code shellcode.sRDI (https://github.com/monoxgas/sRDI): By Monoxgas (https://twitter.com/monoxgas), this tool can convert existing naticcve DLL into PIC, which can then be injected as regular shellcode.Pe2Sh (https://github.com/hasherezade/pe_to_shellcode): By Hasherazade (https://twitter.com/hasherezade), this tool can convert an existing native EXE into PIC shellcode, which can also be run as a normal EXE.
LI Encoders vs LD Encoders
Inceptor can encode, compress, or encrypt shellcode using different means. While developing the tool, I started differentiating between what I call loader-independent (LI) encoding, and loader-dependent (LD) encoding.Loader-independent encoding is a type of encoding not managed by the template chosen by the user (loader). This usually means that the decoding stub is not part of the template, but embedded in the shellcode itself. Inceptor offers this kind of feature using the open-source tool sgn (https://github.com/EgeBalci/sgn), which is used to make the payload polymorphic and undetectable (https://www.kitploit.com/search/label/Undetectable) using common signature detection.Even strong at it is, Shikata-Ga-Nai is not really suitable for certain templates. For this reason, Inceptor also implements Loader-dependent encoders, which are designed to let the loader taking care of the decoding. As such, LD encoders install the decoding stub directly in the template. This kind of encoders, as implemented within Inceptor, are also "Chainable", meaning they can be chained together to encode a payload.While using a chain of encoders can sometimes improve the obfuscation (https://www.kitploit.com/search/label/Obfuscation) of a given payload, this technique can also expose multiple decoding routines, which can help Defenders to design signatures against them. For this reason, Inceptor offers multiple ways to obfuscate the final artifacts, hardening the RE process.At the time of writing, the public version of Inceptor has been provided with the following encoders/compressors/encryptors:Native XorNop (Insertion).NET HexBase64XorNop (Insertion)AESZlibRLEPowerShell HexBase64XorNop (Insertion)AESInceptor can validate an encoding chain both statically and dynamically, statically checking the decoders' input/output types, and also dynamically verifying the implementation with an independent implementation.At any time, a user can easily validate a chain using the chain-validate.py utility.
AV Evasion Mechanisms

___________________________
@hacking_Attack
@Hacking_Video

Inceptor also natively implements AV Evasion mechanisms, and as such, it offers the possibility to include AV evasion features to the payload in the form of "modules" (plugins).The plugins which can be embedded are: AMSI bypass WLDP bypass ETW bypass Sandbox (Behavioural) Deception
EDR Evasion Mechanisms
Inceptor also implements EDR Evasion mechanisms, such as full unhooking, direct syscall invocation and manual DLL mapping. Direct Syscalls are implemented in C# using the outstanding "DInvoke (https://github.com/TheWover/DInvoke)" project, again by TheWover (https://github.com/phra/PEzor). In C/C++, Syscalls are implemented using SysWhispers (https://github.com/jthuraisamy/SysWhispers) and SysWhispers2 (https://github.com/jthuraisamy/SysWhispers2) projects, by Jackson_T (https://twitter.com/Jackson_T). In addition, Inceptor has built-in support for x86 Syscalls as well.As the AV bypass features, these features can be enabled as modules, with the only difference that they require operating on a template which supports them. The techniques implemented so far are: Full Unhooking Manual DLL Mapping Direct Syscalls
Obfuscation
Inceptor supports payload obfuscation by using external utils, such as ConfuserEx (https://github.com/mkaring/ConfuserEx)and Chameleon (https://github.com/klezVirus/chameleon), and provides support for C/C++ obfuscation using LLVM-Obfuscator (https://github.com/klezVirus/obfuscator), which is an IR-based obfuscator using the LLVM compilation platform. PowerShell C# C/C++
Code Signing
Another feature of Inceptor is that it can code sign the resulting binary/dll by using the tool CarbonCopy (https://github.com/paranoidninja/CarbonCopy)Usually, files signed with code signing certificates (https://www.kitploit.com/search/label/Certificates) are less strictly analysed. Many anti-malware products don't validate/verify these certificates.
Workflow
The full workflow can be summarized in the following high-level, and simplified scheme:

___________________________
@hacking_Attack
@Hacking_Video

Installation
Inceptor has been designed to work on Windows. The update-config.py utility can locate the required Microsoft binaries and update the configuration accordingly. It might be required to install Microsoft Build Tools, the Windows SDK, and Visual Studio, update-config.py will guide the user on how to install the required dependencies.git clone --recursive https://github.com/klezVirus/inceptor.git
cd inceptor
virtualenv venv
venv\Scripts\activate.bat
pip install -r requirements.txt
cd inceptor
python update-config.py

Useful Notes

Default Loaders
The current version of Inceptor locates a specific template using a simple naming convention (don't change template names), and the set of arguments given by the user. Among the arguments, there is also the loader (-t). If not specified, the loader will be picked-up as a function of the file to pack, following this simple schema:$ python inceptor.py -hh

[*] Default Loaders
Input File Extension SpecialCondition Guessed Filetype Default Loader Default Template
0 .raw NaN Shellcode Simple Loader Classic
1 .exe .NET Dotnet Executable Donut Classic
2 .exe NaN Native Executable Pe2Shellcode PE Load
3 .dll NaN Native Library sRDI Classic

Template name convention
It's very important to understand also the template name convention, to avoid misinterpreting an artifact behaviour.Classic: a classic template usually means it uses the VirtualAlloc/VirtualAllocEx and CreateThread/CreateRemoteThread API to allocate and execute arbitrary codeDinvoke: if a template contains only dinvoke (e.g classic-dinvoke.cs), it means it uses dynamic function resolution feature of dinvokedinvoke-subtechnique: a template containing dinvoke followed by another keyword is using a particular feature of dinvoke, like manual_mapping, overload_mapping, or syscallsSyscalls: as the name suggest, this template is using syscallsPE Load: this template tries to map a full PE into memory, without transforming itAssembly Load: this template tries to execute a .NET assembly using reflection
Usage
$ usage: inceptor.py [-h] [-hh] [-Z] {native,dotnet,powershell} ...

inceptor: A Windows-based PE Packing framework designed to help
Red Team Operators to bypass common AV and EDR solutions

positional arguments:
{native,dotnet,powershell}
native Native Binaries Generator
dotnet .NET Binaries Generator
powershell PowerShell Wrapper Scripts Generator

optional arguments:
-h, --help show this help message and exit
-hh Show functional table
-Z, --check Check file against ThreatCheck

Next Developments
New Template EngineNew TemplatesNew EncodersC# Code-Based obfuscation
Resources
Inceptor - Bypass AV-EDR solutions combining well known techniques (https://github.com/klezVirus/inceptor/blob/main/slides/Inceptor%20-%20Bypass%20AV-EDR%20solutions%20combining%20well%20known%20techniques.pdf)A tale of EDR bypass methods (https://s3cur3th1ssh1t.github.io/A-tale-of-EDR-bypass-methods)

Download Inceptor (https://github.com/klezVirus/inceptor)

___________________________
@hacking_Attack
@Hacking_Video

KitPloit - PenTest Tools!
Inceptor - Template-Driven AV/EDR Evasion Framework

https://blogger.googleusercontent.com/img/a/AVvXsEjMvp71667jwAxf10_rXDiDkFYyHXKpBYUY34Z1QEbtEyfAja5ezfO_ba2zZkkdfXFgc5-TreFrgs9bicdvBhrWHvvcWW9wo8t7YVqVUBw4-OrTpR2aBO5MZhT-zfdV6f9tl-TyFJDZZQmSSuvDvNelQUNDUkFdAXn9-IL-Kf4IWfAOsFrq-sN4HgS2KA=w640-h348 Modern Penetration testing and Red Teaming often requires to bypass common AV/EDR appliances in order to execute code on a target. With time, defenses are becoming more complex and inherently more difficult to bypass consistently.

Inceptor is a tool which can help to automate great part of this process, hopefully requiring no further effort. FeaturesInceptor is a template-based PE packer for Windows, designed to help penetration testers and red teamers to bypass common AV and EDR solutions. Inceptor has been designed with a focus on usability, and to allow extensive user customisation.

To have a good overview of what it was implemented and why, it might be useful to tak a look to the following resources:

* The path to code execution in the era of EDR, Next-Gen AVs, and AMSI
* Inceptor - Bypass AV-EDR solutions combining well known techniques Shellcode Transformation/LoadingInceptor is able to convert existing EXE/DLL into shellcode using various open-source converters:

* Donut: Donut is "The Converter". This tool is more like a piece of art by TheWover, and can be used to transform Native binaries, DLL, and .Net binaries into position independent code shellcode.
* sRDI: By Monoxgas, this tool can convert existing naticcve DLL into PIC, which can then be injected as regular shellcode.
* Pe2Sh: By Hasherazade, this tool can convert an existing native EXE into PIC shellcode, which can also be run as a normal EXE. LI Encoders vs LD EncodersInceptor can encode, compress, or encrypt shellcode using different means. While developing the tool, I started differentiating between what I call loader-independent (LI) encoding, and loader-dependent (LD) encoding.

Loader-independent encoding is a type of encoding not managed by the template chosen by the user (loader). This usually means that the decoding stub is not part of the template, but embedded in the shellcode itself. Inceptor offers this kind of feature using the open-source tool sgn, which is used to make the payload polymorphic and undetectable using common signature detection.

Even strong at it is, Shikata-Ga-Nai is not really suitable for certain templates. For this reason, Inceptor also implements Loader-dependent encoders, which are designed to let the loader taking care of the decoding. As such, LD encoders install the decoding stub directly in the template. This kind of encoders, as implemented within Inceptor, are also "Chainable", meaning they can be chained together to encode a payload.

While using a chain of encoders can sometimes improve the obfuscation of a given payload, this technique can also expose multiple decoding routines, which can help Defenders to design signatures against them. For this reason, Inceptor offers multiple ways to obfuscate the final artifacts, hardening the RE process.

At the time of writing, the public version of Inceptor has been provided with the following encoders/compressors/encryptors:

* Native
* Xor
* Nop (Insertion)

* .NET
* Hex
* Base64
* Xor
* Nop (Insertion)
* AES
* Zlib
* RLE

* PowerShell
* Hex
* Base64
* Xor
* Nop (Insertion)
* AES
Inceptor can validate an encoding chain both statically and dynamically, statically checking the decoders' input/output types, and also dynamically verifying the implementation with an independent implementation.

At any time, a user can easily validate a chain using the chain-validate.pyutility. AV Evasion MechanismsInceptor also natively implements AV Evasion mechanisms, and as[...]

___________________________
@hacking_Attack
@Hacking_Video