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

@Hacking_Video
@Hacking_attack
Download Telegram
Subdomain Enumeration

Open Source Intelligence gathering toolContinue reading on Medium »
Read more...
MY First Bug In Hackerone

Hello My Dear Buggies!!!Continue reading on Medium »
Read more...
Bypass Rate Limit — A blank space leads to this random encounter!

Hello All, Hope you are having a great time!Continue reading on InfoSec Write-ups »
Read more...
Further the state of O365 security by authoring a PowerShell (https://www.kitploit.com/search/label/PowerShell) script that automates the security assessment of Microsoft Office 365 environments.
Setup 365Inspect requires the administrative PowerShell modules for Microsoft Online, Azure AD (We recommend installing the AzureADPreview module), Exchange administration, Microsoft Graph, Microsoft Intune, Microsoft Teams, and Sharepoint administration. The 365Inspect.ps1 PowerShell script will validate the installed modules. If you do not have these modules installed, you will be prompted to install them, and with your approval, the script will attempt installation. Otherwise, you should be able to install them with the following commands in an administrative PowerShell prompt, or by following the instructions at the references below: Install-Module -Name MSOnline

Install-Module -Name AzureADPreview

Install-Module -Name ExchangeOnlineManagement

Install-Module -Name Microsoft.Online.SharePoint.PowerShell

Install-Module -Name Microsoft.Graph

Install-Module -Name MicrosoftTeams

Install-Module -Name Microsoft.Graph.Intune
Install MSOnline PowerShell (https://docs.microsoft.com/en-us/powershell/azure/active-directory/install-msonlinev1?view=azureadps-1.0) Install Azure AD PowerShell (https://docs.microsoft.com/en-us/powershell/module/azuread/?view=azureadps-2.0) Install Exchange Online PowerShell (https://docs.microsoft.com/en-us/powershell/exchange/exchange-online-powershell-v2?view=exchange-ps) Install SharePoint (https://docs.microsoft.com/en-us/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) Install Microsoft Graph SDK (https://docs.microsoft.com/en-us/graph/powershell/installation) Install Microsoft Teams PowerShell Module (https://docs.microsoft.com/en-us/microsoftteams/teams-powershell-install) Install Microsoft Intune PowerShell SDK (https://github.com/microsoft/Intune-PowerShell-SDK) Once the above are installed, download the 365Inspect source code folder from Github using your browser or by using git clone. As you will run 365Inspect with administrative privileges, you should place it in a logical location and make sure the contents of the folder are readable and writable only by the administrative user. This is especially important if you intend to install 365Inspect in a location where it will be executed frequently or used as part of an automated (https://www.kitploit.com/search/label/Automated) process. Usage To run 365Inspect, open a PowerShell console and navigate to the folder you downloaded 365Inspect into: cd 365Inspect
You will interact with 365Inspect by executing the main script file, 365Inspect.ps1, from within the PowerShell command prompt. All 365Inspect requires to inspect your O365 tenant is access via an O365 account with proper permissions, so most of the command line (https://www.kitploit.com/search/label/Command%20Line) parameters relate to the organization being assessed and the method of authentication. Execution of 365Inspect looks like this: .\365Inspect.ps1 -OrgName -OutPath -Auth
For example, to log in by entering your credentials (https://www.kitploit.com/search/label/Credentials) in a browser with MFA support: .\365Inspect.ps1 -OrgName mycompany -OutPath ..\365_report -Auth MFA
365Inspect can be run with only specified Inspector modules, or conversely, by excluding specified modules. For example, to log in by entering your credentials in a browser with MFA support: .\365Inspect.ps1 -OrgName mycompany -OutPath ..\365_report -Auth MFA -SelectedInspectors inspector1, inspector2
or .\365Inspect.ps1 -OrgName mycompany -OutPath ..\365_report -Auth MFA -ExcludedInspectors inspector1, inspector2, inspector3

___________________________
@hacking_Attack
@Hacking_Video
# to fetch these transport rules within this module; assume main 365Inspect harness has logged us in already.
$safe_attachment_bypass_rules = (Get-TransportRule | Where { $_.SetHeaderName -eq "X-MS-Exchange-Organization-SkipSafeAttachmentProcessing" }).Identity

# If some of the parsed O365 objects were found to have the security flaw this module is inspecting for,
# return a list of strings representing those objects. This is what will end up as the "Affected Objects"
# field in the report.
If ($safe_attachment_bypass_rules.Count -ne 0) {
return $safe_attachment_bypass_rules
}

# If none of the parsed O365 obj ects were found to have the security flaw this module is inspecting for,
# returning $null indicates to 365Inspect that there were no findings for this module.
return $null
}

# Return the results of invoking the inspector function.
return Inspect-BypassingSafeAttachments
Example .json file, BypassingSafeAttachments.json: Rules screen in the Exchange Admin Center. Look for the offending rules and begin the process of assessing who created them and whether they are necessary to the continued function of your organization. If they are not, remove the rules.", "AffectedObjects": "", "References": [ { "Url": "https://docs.microsoft.com/en-us/exchange/security-and-compliance/mail-flow-rules/manage-mail-flow-rules", "Text": "Manage Mail Flow Rules in Exchange Online" }, { "Url": "https://www.undocumented-features.com/2018/05/10/atp-safe-attachments-safe-links-and-anti-phishing-policies-or-all-the-policies-you-can-shake-a-stick-at/#Bypass_Safe_Attachments_Processing", "Text": "Undocumented Features: Safe Attachments, Safe Links, and Anti-Phishing Policies" } ] }'>{
"FindingName": "Do Not Bypass the Safe Attachments Filter",
"Description": "In Exchange, it is possible to create mail transport rules that bypass the Safe Attachments detection capability. The rules listed above bypass the Safe Attachments capability. Consider revie1wing these rules, as bypassing the Safe Attachments capability even for a subset of senders could be considered insecure depending on the context or may be an indicator of compromise.",
"Remediation": "Navigate to the Mail Flow -> Rules screen in the Exchange Admin Center. Look for the offending rules and begin the process of assessing who created them and whether they are necessary to the continued function of your organization. If they are not, remove the rules.",
"AffectedObjects": "",
"References": [
{
"Url": "https://docs.microsoft.com/en-us/exchange/security-and-compliance/mail-flow-rules/manage-mail-flow-rules",
"Text": "Manage Mail Flow Rules in Exch ange Online"
},
{
"Url": "https://www.undocumented-features.com/2018/05/10/atp-safe-attachments-safe-links-and-anti-phishing-policies-or-all-the-policies-you-can-shake-a-stick-at/#Bypass_Safe_Attachments_Processing",
"Text": "Undocumented Features: Safe Attachments, Safe Links, and Anti-Phishing Policies"
}
]
}
Once you drop these two files in the .\inspectors folder, they are considered part of 365Inspect's module inventory and will run the next time you execute 365Inspect. You have just created the BypassingSafeAttachments Inspector module. That's all! 365Inspect will throw a pretty loud and ugly error if something in your module doesn't work or doesn't follow 365Inspect conventions, so monitor the command line output. About Security 365Inspect is a script harness that runs other inspector script modules stored in the .\inspectors folder. As with any other script you may run with elevated privileges, you should observe certain security hygiene practices: No untrusted user should have write access to the 365Inspect folder/files, as that user could then overwrite scripts or templates therein and induce you to run malicious code. No script module should be placed in .\inspectors unless you trust the source of that script module.

___________________________
@hacking_Attack
@Hacking_Video