SQL 2012 transaction log grows but not DB size

Good Day,

We are experiencing an issue where one of our SQL 2012 database transaction logs is growing at an alarming rate (over 1TB in less than 18 hours) while the database has not grown any.

Is there a way to determine what is causing the transaction log to grow? Whether it is a stored procedure or used defined procedure that is causing the issue?

Thanks,

David Brockstedt