Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PoC schedule-based malware check #7199

Closed
woodruffw opened this issue Jan 7, 2020 · 2 comments
Closed

PoC schedule-based malware check #7199

woodruffw opened this issue Jan 7, 2020 · 2 comments
Assignees
Labels
malware-detection Issues related to automated malware detection.

Comments

@woodruffw
Copy link
Member

Like #7198, we'll need a schedule-based malware check for proofing.

The current proposal: a scheduled check for complete turnovers (i.e., no original or previous maintainers/role-holders remaining) in package ownership, graded against other suspicious indicators (IPs not previously seen for the package and/or its maintainers, new maintainers(s) are not in the community of any the the previous maintainers beyond a fixed window).

See #7096.

@woodruffw woodruffw self-assigned this Jan 7, 2020
@woodruffw woodruffw added the malware-detection Issues related to automated malware detection. label Jan 7, 2020
@xmunoz
Copy link
Contributor

xmunoz commented Jan 7, 2020

This might be too complicated for v1, but I think the idea behind sourcerank is really interesting:
https://libraries.io/pypi/requests

A high score combined with complete turnovers might be an interesting signal.

@woodruffw
Copy link
Member Author

Merged; will close when this hits master.

@xmunoz xmunoz closed this as completed Feb 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
malware-detection Issues related to automated malware detection.
Projects
None yet
Development

No branches or pull requests

2 participants