Anti-pattern name for firing events on an object member supplied at instantiation?

An object requires it be instantiated with an object upon which it can call a method to register than an event has occurred — rather than the instantiating code listening for events.

Is this an anti-pattern? If so, does it have a name?

Is there a reason to code this way?