Potential use of proprietary source code in ReactOS

I am opening this issue concerning a matter of significant urgency and importance related to the ReactOS. There are sections of the source code employed within this project bear a striking resemblance to proprietary source code owned by Microsoft Corporation. The sections of the code that are not just similar, but identical to the leaked Windows source code. This isn't about a minor resemblance or shared concepts; it's a clear-cut case of using proprietary code that was never meant to be public. 

The team's stance so far has been to deny any possibility of this happening. However, the evidence speaks for itself. Ignoring this issue or dismissing concerns isn't going to make it go away. Using leaked code is not only unethical but also illegal. Given the nature of this situation, I am concerned that this involve the unauthorized use of copyrighted material, specifically:

1. https://github.com/reactos/reactos/blob/master/ntoskrnl/ob/obinit.c: I've identified troubling similarities between your implementation of ObpTypeMapping, ObpDirectoryMapping, and ObpSymbolicLinkMapping structures and those found in the leaked Windows NT 4 source code. While the formatting between your code and the leaked code may differ, the underlying structure and the sequence of values, remain markedly similar-in some cases, identically.
2. https://github.com/reactos/reactos/blob/master/drivers/base/beep/beep.c: The BeepCleanup function presents a particularly striking example of code resemblance with leaked NT 4 sources. Despite fewer comments in ReactOS and some variable names starting with uppercase (in contrast to the original code) the core structure and logic remain virtually unchanged. Furthermore, both implementations exhibit the unusual practice of casting a function call to void. This uncommon coding style further highlights the parallels between the two codebases.
3. https://github.com/reactos/reactos/blob/master/drivers/base/null/null.c: The functions labeled NullRead, NullWrite, and NullDispatch within the ReactOS exhibit an uncanny resemblance to NlsRead, NlsWrite, and NlsDispatch from NT 4, respectively. Despite the alteration of function names, the body of the code, particularly the order of switch-case statements and the implementations within, are essentially identical to those found in the NT 4 source. This direct replication of logic and structure, while only the function names have been changed, points to a clear case of copy-paste from the proprietary NT 4 codebase.

Such striking resemblances raise serious questions about the originality and legality of your development practices, especially given public commitments to clean room reverse engineering methods. The presence of code that mirrors the leaked Windows NT 4 source so closely, cannot be dismissed as coincidental or trivial. I have undertaken a comparison of the mentioned source code parts from both ReactOS and the NT 4 code found on GitHub, removing empty lines and comments to facilitate a clearer comparison. The evidence, showcasing the identical nature of the code in both ReactOS and the copyrighted NT 4 source, is undeniable. For further evidence, please see the comparative images: https://imgur.com/a/bO8Lf4n

Given these circumstances, I request a thorough and transparent public explanation of:

1. the origins of the contentious code within ReactOS with evidence of so called clean-room reverse engineering methods used by author of indicated plagiarism
2. the measures you took to address and rectify this situation during the audit and why this has not be cleaned up as code appears to be committed in 2007 before the end of an audit

Failure to address these issues comprehensively and transparently will leave me with no choice but to make my findings public in all possible places. This is not about seeking conflict; it's about demanding accountability and ensuring that ReactOS adheres to legal and ethical standards.