If you find an exposed token in the wild, for a service supported by GitHub Secret Scanning, uploading it to a Gist will either immediately revoke it or notify the owner.
it works for any gist, public or private. it doesn't need to follow a certain format. it's just based on how the secret itself is formatted—it works for secrets that have a predictable pattern, like the AWSK prefix for Amazon keys.
if algolia keys have this predictable pattern, then they can enroll in secret scanning. If they don't then they probably can't
The purpose of command and control servers is to send and receive data to victims devices.
A secondary goal is to do so while evading detection. This is why many threat actors piggy-back off of legitimate services, it disguises the malware communications and avoids directly exposing the upstream C2 instance.
The main use case, in my opinion, is for tests/CI. SQLite has traditionally been used to quickly run tests, however, if your actual infra uses PostgreSQL then the value is limited.
I think they meant sqlite is often used in CI/CD testing environments as an alternative to running a client/server database in these environments. For simple crud webapps, or frameworks that are db agnostic it works well.
reply