- Home
- Skills
- Testing & Debugging
- Repo Malware Scanner
Works with the AI Agents you already use
Repo Malware Scanner
Scan a cloned repo for hidden supply-chain payloads before npm install. Flags padded one-liners, eval wrappers, require hijacks, env dumps, and HTTP inside config
$6
/moSubscription · cancel anytime
Secure checkout via Stripe
- Always the latest version
- Delivered live to your agent via MCP
- Cancel anytime, access ends at period end
Repo Malware Scanner
Example session with this skill installed
I just cloned this open-source tool. Can you scan the current directory for any suspicious code before I run npm install?
- Read your context and instructions
- Compiled the repo malware scanner
The malware scan has completed for the current workspace. I have identified one CRITICAL finding that requires your immediate attention before you proceed with installation.
Security Scan Results
| File Path | Line | Level | Finding |
|---|---|---|---|
src/utils/init.js | 42 | CRITICAL | eval(variable) - Possible obfuscated code execution detected |
vite.config.ts | 12 | CRITICAL | fetch in config - Configuration files should not call the network |
dist/bundle.min.js | 1 | WARNING | Long minified line detected (potential obfuscation) |
scripts/post-build.js | 89 | CRITICAL | JSON.stringify(process.env) - Credential dump pattern detected |
CRITICAL: Do not run npm install or npm run dev at this time.
The scan detected a credential dump pattern in your post-build script and a network request originating from your Vite configuration. These are high-risk indicators of a supply-chain attack designed to exfiltrate your .env variables.
Next steps
- Review line 89 in
scripts/post-build.jsto see why it is accessing the fullprocess.envobject. - Inspect
vite.config.tsto determine why it is usingfetchduring the build process. - Delete the repository if these findings cannot be verified as intentional and safe.
Subscription · always the latest version
- Secure checkout via Stripe
- Cancel anytime
- Delivered live via MCP
About this skill
Static scan for npm/JS supply-chain injections. Point it at a folder before you install, build, or run untrusted scripts.
It looks for:
- Lines padded with hundreds of spaces to hide a payload off-screen
- eval(variable) and Function-constructor wrappers
- Node require hijacking (global.require)
- JSON dump of process.env
- Base64 decode plus eval/exec
- Known stealer fingerprints
- Network calls inside vite/next/babel config files
Python 3 only. No extra packages. No network.
CRITICAL findings: do not npm install until those lines are explained. A clean scan is not a full antivirus — it only matches these fingerprints.
Use it when you clone a package, vendor a dependency, or review a skill/MCP folder.
Static fingerprints only — not a full antivirus. Skips node_modules, dist, build, .git. Does not unpack minified vendor bundles or catch novel obfuscation. Clean (exit 0) means none of these patterns matched, not that the repo is safe. Needs Python 3 on the machine; does not call the network.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free forever
No account required to browse
Trust & safety
Security scan
Security scan passed 9 days ago
Requires
Permissions
File Scopes
The agent runs python3 scripts/repo-malware-scan.py on the folder you name. It only reads source files. It does not install packages, call the network, or write the repo. CRITICAL exit code 1 means do not npm install until you inspect the cited lines.