Unexpected repository “updated” timestamps with no visible changes

[devlopersabbir]

🏷️ Discussion Type

Bug

Body

Hi everyone,

I noticed something unusual in my GitHub account and I’m not sure if it’s a bug or expected behavior.

Around 14 hours ago, many of my older repositories all showed the same “updated” timestamp in the repository list/activity view. It looks like they were modified at the same time.

However, when I open each repository:

There are no new commits
No changes in files
No visible updates in commit history or branches

This is confusing because the repository overview suggests activity, but inside the repositories nothing appears to have changed.

I’m trying to understand:

What could cause multiple repositories to update at the same time?
Is this a UI/cache issue or some background system process?
Has anyone experienced similar behavior?

Any clarification would be appreciated.

Thanks!

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[mariaspatani]

Hi! This behavior can actually happen on GitHub and is usually not a bug.

A few possible reasons:

1. Background processes:
   GitHub may run maintenance tasks like reindexing, dependency scanning, or security checks, which can update the repository’s "last updated" timestamp without visible code changes.

2. Branch or metadata updates:
   Even small changes like:

   • Updating default branch settings
   • Syncing forks
   • Changing repository settings
     can trigger an updated timestamp.

3. Actions or automated workflows:
   If GitHub Actions or bots are enabled, they might update internal metadata without modifying files.

4. Cache/UI refresh:
   Sometimes the UI reflects a refresh or cache update rather than an actual commit change.

5. Organization-wide updates:
   If multiple repos are affected at the same time, it could be due to a system-wide update or maintenance.

Since you’re not seeing any commits or file changes, this is likely expected behavior rather than a bug.

If it continues frequently, you could check:

• “Insights → Network/Activity”
• GitHub Actions logs (if enabled)

Hope this helps clarify things!

[habib33-3]

I discovered a suspicious .bat script that appears to have been used to manipulate Git history. It alters commit metadata such as commit time and committer identity, making changes look like they originated from previously authenticated commits.

The script also modifies .gitignore to exclude sensitive files like .env, and adds multiple unknown .bat files to the ignore list to keep them hidden from version control.

Additionally, several configuration files—including eslint.config, postcss.config, and tailwind.config—were tampered with. Obfuscated code was appended at the bottom of these files, positioned in a way that makes it easy to overlook during normal review.

On the backend side, critical files like main.ts or server.ts contain suspicious IIFE (Immediately Invoked Function Expressions). These functions decode an unknown buffer stream and perform POST requests to a dynamically decoded URL, indicating potential malicious behavior.

This issue has impacted multiple repositories across both my work organization and personal projects.