.+. +.

+*% *@@

++;. *:@ .

+* + & +@

;:+.:: .+ @.@

+:+; *. * .*.%

:@+.&. *: .*. %;.@;

+ @.;%. ;* ;+ .@@ * @

@;+%.*&+;@+;. ;+;+.&% ** &.

++@;+%*&&**+ ;:; :+;..%+%%;@*.*.+

*.%;+&@&%.;@; .:+. ;+. :*+ %&*&+:@.*:

.%.%*;&:;+:@&&+. +: :*..+%&%:++:@.*%;*;

+*+;&&&+ @%%&+ * + .%%%@ .%&&;;@%

.*:%*%&+;+@%+ .*: .+; ;&@*;;@%+@+;:

:@;;*&&*+&&&+ .+;. ;*: ;&&&++&&*;:++

.;:+%; +&%@ * *. ;%&*. .@@:;:

*;*: *&&% .+ +: .@&&%.:;+*;

;%;+.+*&&*:;*. @::;%&** ;*%*

:@*@+@@ **@*@@+

.;:. .:;;

osxploit

REproc

March 8, 2026 informational

The "Hidden" Capabilities of proc_* Calls

What is the extent to which you could permissively leverage metadata from another process's runtime? This writeup will (probably) answer the question, if you have such.

discussion — hosted on github via giscus

back to research