So this has to be a bug right? https://norig.myfootballnow.com/watch/651#116236

First game in 0.4.6, and first time I see this me too...

https://nfl.myfootballnow.com/watch/7671#1371478

So it has to be a 0.4.6 issue...

...counts as a sack, too! lol

It happens

https://ftw.usatoday.com/2016/08/cleveland-browns-qb-back-endzone-oops-fail-safety-video

My gut is screaming that if we really took note, we might find more than a few of the extaordinary sack numbers (frankly anything above 1 being a sack is extraordinary given RL NFL rulebook) in 4.6 are a direct result of the QB walking out of the end zone.
...and the assignment of said sack to the closest defensive player (i would bet a dogecoin lol it's the closest DL - with the highest or 2nd highest acc) is part of the inflation of overall sack numbers.
I'd like to note, tho we old timers recon 4.4, perhaps some of the inflated sack totals are in correlation to changes made to base speed, and - potentially - a new bug previously unexposed in the already known bug of sack/sack allowed asignments.
A new ripple, if one would allow, to something we've already seen in the fine print reviews.

I hope I put the slingshot of sphaghetti into something understandable lol :)
I just see a pattern, and I think it's related to a lagacy assignment bug, and it's been exposed in 4.6 due to changes in the static "X" of any parabolic effect.

WHEW!
(not proofread)

Clarity:
...numbers (frankly anything above 1 being a sack in the event of the QB exiting the back of the end zone is extraordinary given RL NFL rulebook) in 4.6 ...