AWS Lambda, a popular serverless computing service, faces several potential hacking threats if not adequately secured. These risks include configuration mistakes leading to public exposure or overly permissive IAM roles, as well as code vulnerabilities like command and SQL injection. Attackers might exploit event-data injection by manipulating data or utilizing cross-site scripting. To mitigate these threats, the document recommends strategies such as adhering to the principle of least privilege, rigorously validating inputs, and diligently managing dependencies. Furthermore, the text emphasizes the importance of code reviews, continuous monitoring, secure environment configurations, and proper secrets management to bolster Lambda function security.