twistrs
noseyparker
Our great sponsors
twistrs | noseyparker | |
---|---|---|
8 | 13 | |
86 | 1,511 | |
- | 8.7% | |
6.8 | 9.4 | |
6 months ago | 2 days ago | |
Rust | Rust | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
twistrs
- Have I Been Squatted?
-
Domain Permutation - HaveIBeenSquatted & dnstwist
I recently stumbled upon 2 cool domain permutation tools: HIBS & dnstwist
-
Have I Been Squatted? – Check if your domain has been typosquatted
It’s powered by twistrs, a Rust typoesquatting library we authored a while back. It’s not much but I hope you enjoy it – would love to hear your feedback and/or questions!
-
Have I Been Squatted — free DNS typosquatting platform
Regarding your question, we pack a large number of different whois servers in the twistrs library that we then use to perform lookups. I suspect we'll eventually hit the same throttling issue and to be brutally honest, it's unclear what a feasible solution to this would look like at this point in (perhaps throttling whois feature entirely). In your context, where you sending all requests to a single API?
Regarding the domain, the missing vowel should be one of the permutations. If it's not a sensitive domain would you mind opening an issue on twistrs highlighting which domain wasn't caught. If it's sensitive you can simple DM me on Reddit or send an email to juxhin[at]phishdeck.com
-
Have I Been Sqautted – free DNS typosquatting platform
Yes it does, you can take a peak into the internals over here - https://github.com/JuxhinDB/twistrs/blob/3b20ed48c0c567a72d8...
noseyparker
-
Magika: AI powered fast and efficient file type identification
Yes!
Sometimes a file has no extension. Other times the extension is a lie. Still other times, you may be dealing with an unnamed bytestring and wish to know what kind of content it is.
This last case happens quite a lot in Nosey Parker [1], a detector of secrets in textual data. There, it is possible to come across unnamed files in Git history, and it would be useful to the user to still indicate what type of file it seems to be.
I added file type detection based on libmagic to Nosey Parker a while back, but it's not compiled in by default because libmagic is slow and complicates the build process. Also, libmagic is implemented as a large C library whose primary job is parsing, which makes the security side of me jittery.
I will likely add enabled-by-default filetype detection to Nosey Parker using Magika's ONNX model.
[1] https://github.com/praetorian-inc/noseyparker
- GitHub: Can no longer search code without being logged in
- Managing secrets like API keys in Python - Why are so many devs still hardcoding secrets?
-
Show HN: Nosey Parker, a fast and low-noise secrets detector for textual data
Yes and no.
On the one hand, Nosey Parker is effectively a special-purpose `grep` with a bunch of security-relevant patterns built-in, including one for PEM-encoded keys: <https://github.com/praetorian-inc/noseyparker/blob/main/data...>
On the other hand, to naively run the check you describe, you would need access to a copy of all of GitHub, which isn't feasible.
What you can do with Nosey Parker is use its GitHub enumeration features to specify your GitHub organization and a list of GitHub usernames you are interested in, and scan against just those. This will implicitly list all the relevant public repositories, clone them, and scan their entire history.
For your use case, another thing you could do is use the new GitHub code search (<https://cs.github.com>) to regex search for particular keys or tokens. That new search seems to cover lots of the public content available on GitHub.
Also, to put some color on this use case: in offensive security engagements (aka "red team" engagements) at Praetorian, we frequently find leaked credentials or tokens on GitHub or elsewhere, which allow us deeper access into the client's systems. It's a significant problem.
- Nosey Parker, a fast and low-noise secrets detector, now supports enumerating GitHub repositories and writing results in SARIF format
- Nosey Parker, a newer secrets detector, can scan 100GB of Linux kernel commit history in 2 minutes on a laptop, and now can write SARIF output
- Nosey Parker, a fast secrets detector, now enumerates GitHub repos, writes SARIF output, and has 90 default rules
-
Tools for scanning commits?
A tool just got open-sourced called Nosey Parker that scans commits and git history for secrets. You could look at Nosey Parker's source code to see how they scan commits and design your tool based on that.
- Nosey Parker, a new scanner for hardcoded secrets in textual data
What are some alternatives?
dnstwist - Domain name permutation engine for detecting homograph phishing attacks, typo squatting, and brand impersonation
betterscan-ce - Code Scanning/SAST/Static Analysis/Linting using many tools/Scanners + OpenAI GPT with One Report (Code, IaC) - Betterscan Community Edition (CE)
opensquat - The openSquat is an open-source tool for detecting domain look-alikes by searching for newly registered domains that might be impersonating legit domains.
trufflehog - Find and verify credentials
RustScan - 🤖 The Modern Port Scanner 🤖
leaky-repo - Benchmarking repo for secrets scanning
Ockam - Orchestrate end-to-end encryption, cryptographic identities, mutual authentication, and authorization policies between distributed applications – at massive scale.
MyBB - MyBB is a free and open source forum software.
mfaws - A cross-platform CLI tool to manage AWS credentials for MFA-enabled accounts
parse-server - Parse Server for Node.js / Express
noseyparker - Nosey Parker is a command-line program that finds secrets and sensitive information in textual data.