The vulnerability is due to a supply-chain attack where malicious versions of the nx package were published to npm. These malicious versions contained a postinstall script that executed malicious code. This script, referred to as telemetry.js in the security advisory, would scan the user's filesystem for credentials and other sensitive information, and exfiltrate it to a remote server. The vulnerability is not in the nx source code itself, but in the compromised packages that were published. The malicious code was executed by the package manager (e.g., npm, yarn) during the installation of the compromised package, not by the nx application at runtime. Therefore, there are no vulnerable functions within the nx codebase that would appear in a runtime profile of the application. The malicious activity happens at package installation time, outside the normal execution of the nx tool.