|
| 1 | +--- |
| 2 | +title: IntelOwl Improvements and Integrations |
| 3 | +date: 2025-09-01 |
| 4 | +cover: /images/gsoclogo.png |
| 5 | +author: Akshit Maheshwary |
| 6 | +--- |
| 7 | + |
| 8 | +### Introduction |
| 9 | +It has always been on my mind for a while, to contribute to a great open-source project, like IntelOwl, in a significant manner and though I knew about GSoC earlier, I never paid much attention to it . But here I am, finally documenting everything that I have done this summer as part of Google Summer of Code 2025. |
| 10 | +### Pre-GSoC Commits/Discussions. |
| 11 | + |
| 12 | + |
| 13 | +- Added [Androguard Analyzer](https://github.com/intelowlproject/IntelOwl/pull/2555) to reverse engineer APKs |
| 14 | +- Added [NVD CVE Analyzer](https://github.com/intelowlproject/IntelOwl/pull/2560) |
| 15 | +- Added [MobSF Service Analyzer](https://github.com/intelowlproject/IntelOwl/pull/2584) to perform static and dynamic analysis of APKs straight from IntelOwl |
| 16 | + |
| 17 | +These were some of my PRs that got merged after being reviewed by the project maintainers. I'd also started working on other issues as well such as [#2407](https://github.com/intelowlproject/IntelOwl/issues/2407) |
| 18 | +which had improved my understanding around some of the core parts of the architecture of IntelOwl. |
| 19 | + |
| 20 | +# GSoC Scope of Work and Deliverables |
| 21 | + |
| 22 | +GSoC idea that I've been selected for, involved **designing and development of new analyzers** for IntelOwl to enhance the threat intelligence |
| 23 | +capabilites of IntelOwl, further. |
| 24 | + |
| 25 | +Apart from that, I had the opportunity to work on optimising the performance of IntelOwl's sister project [Honeyscanner - A vulnerability analyzer for honeypots](https://github.com/honeynet/honeyscanner) |
| 26 | +which was not in scope of the proposal, but since HoneyScanner analyzer had to be added, as per the initial proposal, so it was worked on as well. |
| 27 | + |
| 28 | +Now I'll proceed with elucidating the work that I've done. |
| 29 | + |
| 30 | +## Addition of New Analyzers |
| 31 | + |
| 32 | +- Added [HuntingAbuseAPI Analyzer](https://github.com/intelowlproject/IntelOwl/pull/2885) which provides an updated list of false positives from all it's services. This API can be queried to verify. if the provided observable is valid or false positive. |
| 33 | +- Updated [GreedyBear Analyzer](https://github.com/intelowlproject/IntelOwl/pull/2902) to fetch the command sequences executed in a honeypot using CommandSequenceAPI from GreedyBear. |
| 34 | +- Integrated [GuardDog](https://github.com/intelowlproject/IntelOwl/pull/2930) to IntelOwl, as part of which 2 analyzers, **GuardDogFile** and **GuardDogGeneric**, have been added in order to scan for malicious pypi, npm and go packages. |
| 35 | +- [ExpandURL Analyzer](https://github.com/intelowlproject/IntelOwl/pull/2920) has been added to IntelOwl, which basically follows the redirection chain for a provided malicious shortened URL and expands it to it's original form for further analysis. |
| 36 | +- Added support for [JoeSandBox](https://github.com/intelowlproject/IntelOwl/pull/2925), as part of which 2 analyzers, JoeSandBoxURL and JoeSandBoxFile, to enhance the malware analysis capabilities of Intelowl for a provided sample of file or URL. |
| 37 | +- [Refactored Flare Capa and Flare Floss analyzers](https://github.com/intelowlproject/IntelOwl/pull/2933) using the traditional analyzer design, in order to solve the problem of managing binaries and tracking updates. |
| 38 | +- Integrated the younger brother [Yara-X Analyzer](https://github.com/intelowlproject/IntelOwl/pull/2980) to provide faster executions from single analysis. Alongside this, [Yara-Forge Rule Repository](https://yarahq.github.io/) has also been integrated to provide enhanced rule set selection, as part of this PR. |
| 39 | +- Added [Honeyscanner Analyzer](https://github.com/intelowlproject/IntelOwl/pull/2982) to provide capability of vulnerability detection in deployed honeypots. |
| 40 | + |
| 41 | +## Optimization of core parts of Honeyscanner |
| 42 | +- As part of the original GSoC proposal, Honeyscanner analyzer was supposed to be integrated, but the pre-existing design of Honeyscanner was such that vulnerability scan for |
| 43 | + a single honeypot deployed over external network would theoretically take more than 2 days to finish. |
| 44 | +- So as part of the integration of honeyscanner analyzer, significant effort has gone into optimizing the various core parts of the program to achieve faster execution times. |
| 45 | +- This PR [Optimization of Core parts of honeyscanner alongside Packaging via pyproject.toml](https://github.com/honeynet/honeyscanner/pull/51) mentions everything that has gone into making honeyscanner viable to integrate into InteOwl. |
| 46 | +- Some highlights: |
| 47 | + - **Reduced the execution** time from ~ 54 hours to ~ 11 minutes for honeypots hosted over external network by leveraging `asyncio` library to perform cooperative scheduling of tasks. |
| 48 | + - **Implemented selective fuzzing** for externally and locally hosted honeypots to optimise the fuzzing that suits the best to each environment. |
| 49 | + - **Optimised tar_bomb attack** to perform concurrent operations, with the help of `asyncio` library. |
| 50 | + |
| 51 | +# Ending Note and Future Work |
| 52 | + |
| 53 | +I really had a great time working on improving IntelOwl, and making some threat analyst's life easier. I couldn't have imagined that I would |
| 54 | +get the opportunity to be part of this year's Google Summer of Code cohort and make an impact in open-source world. |
| 55 | + |
| 56 | +I would like to thank my mentors Matteo, Federico and Daniele, who trusted me to carry out this task and who have constantly helped me getting acquainted to the whole process, |
| 57 | +and have also helped me with any blockers that I faced during this period. I had really insightful discussions with them related to project development which |
| 58 | +has honed my technical skills . |
| 59 | + |
| 60 | +Regarding the future, I'll continue working with the maintainers of IntelOwl in whatever capacity I can, to continously improve the features of |
| 61 | +IntelOwl. I do plan to design and develop IntelChat, through which threat analysts can simply chat with IntelOwl, but this idea is in it's infancy right now 😶🌫️ |
| 62 | + |
| 63 | + |
| 64 | + |
| 65 | + |
| 66 | + |
0 commit comments