Hacking Articles Tips Tricks Videos Tutorials
471 subscribers
65.9K photos
15 videos
157 files
132K links
Exploit
Pentesting
Hacking
Red Team
Blue Team
Kali Linux
Bug Bounty
Black Hat
Cyber security etc

@Hacking_Video
@Hacking_attack
Download Telegram
hacking: security in practice
Use SSH tunnel with VNC for VPS inside VM ?

Hey guys,

is it recommended to use VNC as SSH tunnel inside a VM ?

Or is it unlikely to get hacked connecting within my Host Os? ( I mean technically.)

It's a kali linux working machine.

Personally, I feel better If I use SSH/VNC within a VM. But it's uncomfortably slower.

submitted by /u/Giomio27
[link] [comments]
A story of Host Header injection

Hii all, I am back with a new hacking story . A few days ago, I was hunting on one of the VPD program Where i find a host-head injection…Continue reading on Medium »
Read more...
Hii all, I am back with a new hacking story . A few days ago, I was hunting on one of the VPD program Where i find a host-head injection…Continue reading on Medium » (https://medium.com/@milanjain7906/a-story-of-host-header-injection-c977adbf0889?source=rss------bug_bounty-5)
Hacking Articles Tips Tricks Videos Tutorials
Photo
Kali Linux Tutorials
PersistenceSniper : Powershell Script That Can Be Used By Blue Teams, Incident Responders And System Administrators

PersistenceSniper is a Powershell module that can be used by Blue Teams, Incident Responders and System Administrators to hunt persistences implanted in Windows machines. The script is also available on Powershell Gallery. The tool is under active development with new releases coming out by the week, so make sure to use the up-to-date version! The WhyWhy writing such a tool, you might ask. Well, for starters, I tried looking around and I did not find a tool which suited my particular use case, which was looking for known persistence techniques, automatically, across multiple machines, while also being able to quickly and easily parse and compare results. Sure, Sysinternals’ Autoruns is an amazing tool and it’s definitely worth using, but, given it outputs results in non-standard formats and can’t be run remotely unless you do some shenanigans with its command line equivalent, I did not find it a good fit for me. Plus, some of the techniques I implemented so far in PersistenceSniper have not been implemented into Autoruns yet, as far as I know. Anyway, if what you need is an easy to use, GUI based tool with lots of already implemented features, Autoruns is the way to go, otherwise let PersistenceSniper have a shot, it won’t miss it https://s.w.org/images/core/emoji/14.0.0/72x72/1f642.png UsageUsing PersistenceSniper is as simple as firing up Powershell as Administrator and running:

PS C:> git clone https://github.com/last-byte/PersistenceSniper
PS C:> Import-Module .\PersistenceSniper\PersistenceSniper\PersistenceSniper.psd1
PS C:> Find-AllPersistence

If you prefer sticking to the Powershell Gallery version (which is automatically updated through a Github action every time a new version is pushed here on Github), open up Powershell as Administrator and run:

PS C:> Install-Module PersistenceSniper
PS C:> Import-Module PersistenceSniper
PS C:> Find-AllPersistence

If you need a detailed explanation of how to use the tool or which parameters are available and how they work, PersistenceSniper’s Find-AllPersistencesupports Powershell’s help features, so you can get detailed, updated help by using the following command after importing the module:

Get-Help -Name Find-AllPersistence -Full

If you only want to check for a single persistence technique, you can rely on Find-AllPersistence‘s PersistenceMethodparameter. Say, for example, you only want to check for persistences implanted through the Run and RunOnce registry keys:

PS C:> Find-AllPersistence -PersistenceMethod RunAndRunOnce

The PersistenceMethodparameter uses Powershell’s ValidateSetdirective, so you can tab through it instead of writing down the persistence method of choice.

PersistenceSniper’s Find-AllPersistencereturns an array of objects of type PSCustomObject with the following properties:

$PersistenceObject = [PSCustomObject]@{
‘ComputerName’ = $ComputerName
‘Technique’ = $Technique
‘Classification’ = $Classification
‘Path’ = $Path
‘Value’ = $Value
‘Access Gained’ = $AccessGained
‘Note’ = $Note
‘Reference’ = $Reference
‘Signature’ = Find-CertificateInfo (Get-ExecutableFromCommandLine $Value)
‘IsBuiltinBinary’ = Get-IfBuiltinBinary (Get-ExecutableFromCommandLine $Value)
‘IsLolbin’ = Get-IfLolBin (Get-ExecutableFromCommandLine $Value)
}

This allows for easy output formatting and filtering. Let’s say you only want to see the persistences that will allow the attacker to regain access as NT AUTHORITY\SYSTEM (aka System):

PS C:> Find-AllPersistence | Where-Object “Access Gained” -EQ “System”
https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjoyVEAWzT8w7wj68BR7jAfdMHR4y1wuiH9ZXw6a10Rjdx-cBpFEt1zPVdT9W08n0egP0_gklMhrEsrAf2wMwVPZyFR6Al7lAfgQ_tY-N8g62GtT96xM-RZKkNZiaK7Xv9v[...]

___________________________
@hacking_Attack
@Hacking_Video