Group IB Threat Intelligence and Attribution : Bug-fix - GIB compromised/breached collection fix

[EvgeniyMeteliza]

Please ensure your pull request (PR) adheres to the following guidelines:

• Please refer to our contributing documentation for any questions on submitting a pull request, link: Contribution Guide

Pull Request Checklist

Please check if your PR fulfills the following requirements:

• [x] Testing of all the changes has been performed (for bug fixes / features)
• [x] The readme.html and readme.md have been reviewed and added / updated if needed (for bug fixes / features)
• [x] Use the following format for the PR description: <App Name>: <PR Type> - <PR Description>
• [ ] Provide release notes as part of the PR submission which describe high level points about the changes for the upcoming GA release.
• [ ] Verify all checks are passing.
• [x] Do NOT use the next branch of the forked repo. Create separate feature branch for raising the PR.
• [ ] Do NOT submit updates to dependencies unless it fixes an issue.
• [x] Limit your pull request to one application and submit multiple pull requests if necessary.

  Pull Request Type

Please check the type of change your PR introduces:

• [ ] New App
• [x] Bugfix
• [ ] Feature
• [ ] Code style update (formatting, renaming)
• [ ] Refactoring (no functional changes, no api changes)
• [ ] Documentation
• [ ] Other (please describe):

Release Notes (REQUIRED)

• Fixed compromised/breached collection ingestion.

What is the current behavior? (OPTIONAL)

• Describe the current behavior that you are modifying.

What is the new behavior? (OPTIONAL)

• Describe the behavior or changes that are being added by this PR.

Other information (OPTIONAL)

• Any other information that is important to this PR such as screenshots of how the component looks before and after the change.

Pay close attention to (OPTIONAL)

• Any specific code change or test case points which must be addressed/reviewed at the time of GA release.

Screenshots (if relevant)

---

Thanks for contributing!

[EvgeniyMeteliza]

!scan

[splunk-soar-connectors-bot]

@EvgeniyMeteliza Test results here: https://drive.google.com/file/d/1TIbn8eiB8DE637uj4gVUMQ4bvlQDzUZo/view?usp=drivesdk Please view suggestions in verbose descriptions of failed test outputs and the compile script output, then make changes accordingly

[splunk-soar-connectors-bot]

Hello!

The apps in this repo have been migrated to our new GitHub org https://github.com/splunk-soar-connectors under separate repositories. Kindly re-submit your PR to the repo in the new org for the app you are contributing to.