secure-code-review

Audit source code for exploitable vulnerabilities using attack-surface-driven dataflow analysis.

1|Updated Jul 17, 2026
One-click install
npx skills add https://github.com/anonymous99-Rise/multi-CyberSecurity --skill secure-code-review-anonymous99-rise
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: secure-code-review
Source: https://github.com/anonymous99-Rise/multi-CyberSecurity/tree/main/Skills20260809/secure-code-review
Command: npx skills add https://github.com/anonymous99-Rise/multi-CyberSecurity --skill secure-code-review-anonymous99-rise

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manual code audits often drown in SAST false positives and miss exploitable flaws hidden across files, languages, and supply-chain dependencies. This Skill provides a systematic methodology that prioritizes real attack paths over theoretical defects. ## Core Features & Use Cases - Attack-Surface-Driven Auditing: Enumerate entry points (HTTP routes, message queues, callbacks), trace Source-to-Sink dataflows, and rank findings with a P0-P3 priority matrix. - Multi-Language Vulnerability Patterns: Covers Java, Python, Go, Node.js, PHP, and C# with concrete dangerous-code examples for SQL injection, deserialization, SSRF, SSTI, path traversal, and prototype pollution. - Supply Chain & AI-Assisted Review: Detects dependency confusion, typosquatting, malicious install hooks, and integrates LLM prompt templates with Semgrep/CodeQL pipelines for false-positive filtering and adversarial verification. - Use Case: Given a Java Spring repository, enumerate all unauthenticated endpoints, trace user input to a MyBatis ${} sink, confirm exploitability with a PoC, and produce a CVSS-scored report with a full evidence chain. ## Quick Start Audit this repository for exploitable vulnerabilities by enumerating entry points, tracing dataflows to dangerous sinks, and reporting findings with file and line evidence.

Frequently Asked Questions about secure-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prioritize which code to audit first in a large repository?

Start from the attack surface: enumerate all entry points (HTTP routes, message consumers, callbacks, CLI commands), then trace dataflow from each entry to dangerous sinks. Rank targets with a P0-P3 matrix based on authentication status, data sensitivity, and exploitability.

How to reduce SAST false positives with LLM-assisted code review?

Feed Semgrep or CodeQL SARIF output to an LLM for classification, requiring every confirmed finding to cite file and line numbers plus a full dataflow path. Apply adversarial verification prompts that attempt to disprove each finding before reporting.

What vulnerability patterns differ between Java, Python, and Node.js audits?

Java focuses on deserialization (ObjectInputStream, Fastjson), SpEL injection, and MyBatis ${}拼接; Python on pickle, yaml.unsafe_load, and f-string SQL; Node.js on prototype pollution, NoSQL injection, and node-serialize. The Skill provides per-language dangerous code examples and fixes.

How do I detect malicious packages and dependency confusion?

Scan lockfiles with tools like supply-chain-guard, npm audit, and Trivy, then manually review install hooks, obfuscated strings, hardcoded domains, and network exfiltration behavior in third-party source. Compare published artifacts against source repositories for hidden payloads.

Why do clean SAST scans not guarantee code is secure?

SAST tools miss cross-file attack paths, missing authorization checks, and business logic flaws that have no dangerous-function signature. AI-assisted scans also show high false-negative rates, so findings require manual dataflow verification and PoC validation.

Can this audit methodology integrate into CI/CD pipelines?

Yes, it provides GitHub Actions configurations for Semgrep and CodeQL with SARIF upload, diff-aware incremental scanning, and quality gates. Actions must be pinned by full SHA to prevent supply-chain compromise of the CI toolchain itself.