The vulnerability stems from dependency configuration rather than specific code functions. The affected packages declared a dependency on 'dbs-client' in their requirements.txt, which did not exist in PyPI at the time. This created a dependency confusion vulnerability where attackers could publish a malicious package with that name. The root cause is the package installation process (via setup.py's install_requires) trusting PyPI as the source for this non-existent package, not a vulnerability in any specific function. No code execution functions or specific handlers are mentioned in the provided advisories - the exploit occurs at the package dependency resolution level during installation.