audit-node-modules-with-yara
signature-base
Our great sponsors
audit-node-modules-with-yara | signature-base | |
---|---|---|
4 | 12 | |
19 | 2,329 | |
- | - | |
0.0 | 9.2 | |
about 3 years ago | 7 days ago | |
YARA | YARA | |
- | GNU General Public License v3.0 or later |
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.
audit-node-modules-with-yara
-
Auditing NodeJs modules with YARA rules
To achieve this, I started setting up a small project. It is available at https://github.com/rpgeeganage/audit-node-modules-with-yara
- Node Module supplier chain attack detect using YARA rules
-
Audit Node Module folder with YARA rules
GitHub Repo: https://github.com/rpgeeganage/audit-node-modules-with-yara
signature-base
-
Xzbot: Notes, honeypot, and exploit demo for the xz backdoor (CVE-2024-3094)
> It doesn't matter.
To understand the exact behavior and extend of the backdoor, this does matter. An end to end proof of how it works is exactly what was needed.
> A way to check if servers are vulnerable is probably by querying the package manager
Yes, this has been know since the initial report + later discovering what exact strings are present for the payload.
https://github.com/Neo23x0/signature-base/blob/master/yara/b...
> Not very sophisticated, but it'll work.
Unfortunately, we live in a world with closed-servers and appliances - being able as a customer or pen tester rule out certain class of security issues without having the source/insights available is usually desirable.
- Exploit Outlook CVE-2023-23397 Yara - to detect .msg files exploiting CVE-2023-23397 in Microsoft Outlook
- OneNote Yara rule
-
New Exchange Zero Day rumours [29th September]
* Run the following YARA rules over your logs and aspx files in INSTALL_DIRECTORY/Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\owa\ https://github.com/Neo23x0/signature-base/blob/master/yara/expl_proxyshell.yar
-
Nvidia Breach
If you have a Yara detection platform, Florian Roth’s rules should detect executables signed with this. https://github.com/Neo23x0/signature-base/blob/master/yara/gen_nvidia_leaked_cert.yar.
-
Evidence of a log4j attack found - Now what?
Uses these YARA rules to read JAR, LOG, and TXT files on the system, throwing warnings if any log4shell-looking payloads are found based on those various rules.
- Yara rule to detect ProxyToken exploitation
-
APT29 / NOBELIUM VirusTotal retro hunt results using 12 newly release Yara rules
Rules https://github.com/Neo23x0/signature-base/blob/master/yara/apt_apt29_nobelium_may21.yar
- What are the best FOSS YARA rules you would recommend to deploy?
What are some alternatives?
solidarity - Solidarity is an environment checker for project dependencies across multiple machines.
malware-ioc - Indicators of Compromises (IOC) of our various investigations
jsonschema-bigquery - Convert JSON schema to Google BigQuery schema
Loki - Loki - Simple IOC and YARA Scanner
awesome-yara - A curated list of awesome YARA rules, tools, and people.
PEpper - An open source script to perform malware static analysis on Portable Executable
ThreatHunting - Tools for hunting for threats.
obs-studio-node - libOBS (OBS Studio) for Node.Js, Electron and similar tools
reversinglabs-yara-rules - ReversingLabs YARA Rules
Cerebro - Scripts and lists to help generate YARA friendly string mutations
yara-python - The Python interface for YARA