As soon as I thought about that again this morning, I realized I had missed something in that script. It was only searching for columns whose exact content was c72649779390m4883dada531e6, rather than columns that contained c72649779390m4883dada531e6. So, I revisted that for you, and did that refactoring I mentioned so that this should be a lot easier to read and you can run it from the DNN SQL page if that's easier for you.
CREATE TABLE #results ([table] varchar(255), [column] varchar(255))
DECLARE @T varchar(255), @C varchar(255);
DECLARE Table_Cursor CURSOR FOR
SELECT a.name, b.name
FROM sysobjects a, syscolumns b
WHERE a.id = b.id AND a.xtype = 'u' AND
(b.xtype = 99 OR
b.xtype = 35 OR
b.xtype = 231 OR
b.xtype = 167);
OPEN Table_Cursor;
FETCH NEXT FROM Table_Cursor INTO @T, @C;
WHILE (@@FETCH_STATUS = 0) BEGIN
DECLARE @query as nvarchar(4000)
SET @query = 'insert into #results ([column], [table]) SELECT ''' + @C + ''' as [column], ''' + @T + ''' as [table] where exists (select NULL FROM [' + @T + '] WHERE [' + @C + '] LIKE ''%c72649779390m4883dada531e6%'')'
PRINT @query
EXEC(@query);
FETCH NEXT FROM Table_Cursor INTO @T, @C;
END;
CLOSE Table_Cursor;
DEALLOCATE Table_Cursor;
SELECT * FROM #results
DROP TABLE #results
If it's still clean after running this, there's definitely something quite strange going on with your store module 
Hope it helps!