Resolving Malware and Leaked Secret Issues

Malware and leaked secret findings require you to close them manually using Mark as solved. For leaked secrets, Aikido detects the secret in your version history but leaves invalidation to you, as this happens in an external system and cannot be fully verified. For malware, Aikido flags the infected package but requires you to confirm removal, since automated verification of a clean state is never fully reliable.

More about our Malware Detection and Prevention?

• Read more about Aikido malware detection
• Use Safe Chain to block malicious packages before they are installed

What to do before marking an issue as solved

Leaked secrets

A secret can stay in Git history forever, even after you remove it from the latest commit.

Before marking the issue as solved:

1. Revoke or rotate the secret immediately.
2. Confirm the old secret no longer works.
3. Check that no system still depends on it.
4. Only then mark the issue as solved.

Marking a leaked secret as solved does not mean the secret disappeared from version history. It means you invalidated it and removed the risk.

Malware findings

For malware, Aikido cannot prove removal unless it no longer appears in your dependency data.

Before marking the issue as solved:

1. Remove the affected package from the project.
2. Remove it from the lockfile.
3. Reinstall dependencies if needed.
4. Confirm it no longer appears in the dependency tree.
5. Only then mark the issue as solved.

If you are not sure the malware package is gone, contact Aikido support before marking it as solved.

How to mark an issue as solved

1. Open the issue from the issue list, grouped issue view, or queue sidebar.
2. Open the action menu.

   
3. Select Mark as solved.
4. Review the confirmation prompt.

   
5. Confirm.