# LangChain-Monty Code Interpreter Process Spawn

- **Severity:** Low
- **Signature ID:** `3f1a9c2e-6b7d-4e5a-9c3f-1b2d4e5f6a7b`
- **MITRE ATLAS:** AML.T0050 (Command and Scripting Interpreter)
- **OWASP:** LLM07 (System Prompt Leakage)

## Summary

This rule flags when a program is launched with a command line that mentions langchain-monty, a middleware component that adds code-execution capabilities to LangChain AI agents, in a way that looks like more than routine installation, searching, or testing. It is a baseline observability check, not a confirmed attack detection.

## How the attack works

LangChain agents can use langchain-monty to interpret and run code on behalf of the agent. The rule watches for new processes whose command line includes the langchain-monty name in a form that isn't a package install, a dependency search, or a test run. There is no known exploit or proof-of-concept behind this rule; it exists to establish what normal process activity from this component looks like before anything stronger is built on top of it.

## Why it matters

On its own this rule does not indicate compromise. If langchain-monty is being invoked to execute code outside expected developer workflows, it could mean an agent is running attacker-supplied or unintended code, which could lead to arbitrary command execution in the agent's environment.

## What you can do

- Review any alert to confirm whether the process is a legitimate install, search, or test action versus an actual interpreter invocation.
- Restrict which accounts and environments can invoke langchain-monty directly outside of CI/dev tooling.
- Log and baseline normal langchain-monty process activity in your environment so deviations stand out.
- Treat this as one narrow signal — pair it with broader monitoring of the agent's code-execution behavior rather than relying on it alone.

## Known benign look-alikes

- Developer or CI job running `pip install langchain-monty` / `pip show langchain-monty` during environment setup
- Dependency audit or code search (grep/rg/find/git grep) scanning a repository for references to langchain-monty
- pytest or other test runner invoked against test files that import langchain_monty, where the module name appears in the command line as a file/argument reference rather than an active interpreter invocation
- Documentation build or lint step passing the package name as a plain argument

---
Source: https://www.netzilo.com/threats/langchain-monty-code-interpreter-spawn