# CERT-In / CSIRT-Fin CRAFTY FALCON AI-tool campaign against Indian BFSI

- ID: cert-in-crafty-falcon-bfsi-2026-11
- Reported: 2026-11-04
- Researcher: CERT-In / CSIRT-Fin
- Organization: CERT-In (Indian Computer Emergency Response Team)
- AI role: attacker_uses_ai_as_operator (AI as operator)
- Offensive frameworks: artex, cairn, cyberstrikeai, pentagi
- Confidence in AI involvement: not assessed
- Research / borderline: false
- Last reviewed: 2026-11-06
- Entry page: https://openattacks.ai/attacks/cert-in-crafty-falcon-bfsi-2026-11/
- Entry JSON: https://openattacks.ai/api/attacks/cert-in-crafty-falcon-bfsi-2026-11.json
- Browse title: CRAFTY FALCON campaign against Indian finance
- Editorial summary: CERT-In advisory CIAD-2026-0058 describes CRAFTY FALCON chaining ARTEX, PentAGI, Cairn, and CyberStrikeAI against Indian NBFCs, fintechs, payment firms, and crypto exchanges.
- Evidence class (catalog annotation): Reported campaign
- Source-stated target environments: Cloud & SaaS; Web applications
- Stage hunts and conditional defenses: https://openattacks.ai/api/defenses/cert-in-crafty-falcon-bfsi-2026-11.json

## Technique
CERT-In Advisory CIAD-2026-0058 (Nov 4, 2026) warns of CRAFTY FALCON campaign targeting Indian non-banking financial companies (NBFCs), fintechs, payment aggregators, and cryptocurrency exchanges. Attackers chain multiple open-source agentic offensive AI frameworks: ARTEX (autonomous penetration testing), PentAGI (multi-agent security testing), Cairn (AI-driven web exploitation), and CyberStrikeAI (LLM-powered C2). Campaign features cloud/AWS Lambda pivots for staging-to-production access, AI-driven app reverse-engineering to invoke payment and merchant-settlement APIs from allow-listed infrastructure, Rs. 1 test transfers followed by large mule payouts, cryptocurrency wallet-key theft, comprehensive log deletion, and deliberate retargeting during festive windows when transaction volumes are high and security teams are reduced. CERT-In notes campaign exploits trust in cloud infrastructure and leverages AI agent autonomy to accelerate intrusion timelines from weeks to hours.

## Stack relevance (editorial)
Assessment: not\_assessed. No reviewed applicability annotation is available. Product mentions do not establish victim conditions.
A product mention alone is not a victim-side applicability mapping. Selection does not verify affected versions, permissions or compromise.

## Initial access
Cloud service exploitation, exposed APIs, compromised AWS Lambda functions, credential stuffing against fintech portals

## AI tooling and models
- [ARTEX](https://github.com/RuoJi6/ARTEX) (https://github.com/RuoJi6/ARTEX) — Community-maintained fork; the original repository is unavailable.
- PentAGI (https://github.com/vxcontrol/pentagi)
- CyberStrikeAI (https://github.com/Ed1s0nZ/CyberStrikeAI, https://github.com/aipentest/cyberstrikeai)
- [Cairn](https://github.com/oritera/Cairn) (AI web exploitation harness)
- On-the-fly AI script generation

## Other tooling
- AWS Lambda for staging-to-production pivots
- Custom payment API invocation scripts
- Log deletion tools

## Victims and sectors
Indian non-banking financial companies (NBFCs), fintechs, payment aggregators, cryptocurrency exchanges; festive-season targeting (Diwali, year-end)

## Target geography
- India

## Attribution
CERT-In: CRAFTY FALCON financially motivated campaign; Indian press notes Chinese-linked offensive AI frameworks; no confirmed state nexus in CERT-In advisory

## Scale and metrics
Active since at least Oct 2026; Rs. 1 test transfers followed by large payouts; multiple NBFCs and fintechs compromised; festive-window retargeting pattern

## Attack flow
Catalog reconstruction of the supplied source account. Unknowns and research caveats are preserved.
### initial-recon: AI agent reconnaissance [execution]
AI agent reconnaissance
Evidence: https://www.cert-in.org.in/s2cMainServlet?pageid=PUBVLNOTES02&VLCODE=CIAD-2026-0058

### cloud-pivot: AWS Lambda staging-to-production pivot [execution]
AWS Lambda staging-to-production pivot
Evidence: https://www.cert-in.org.in/s2cMainServlet?pageid=PUBVLNOTES02&VLCODE=CIAD-2026-0058

### api-abuse: Payment/merchant API invocation [execution]
Payment/merchant API invocation
Evidence: https://www.cert-in.org.in/s2cMainServlet?pageid=PUBVLNOTES02&VLCODE=CIAD-2026-0058

### test-transfer: Rs. 1 test transfer [execution]
Rs. 1 test transfer
Evidence: https://indianexpress.com/article/technology/tech-news-technology/cert-in-crafty-falcon-ai-driven-hacking-campaign-fintech-10951672/

### fund-theft: Large mule payouts [impact]
Large mule payouts
Evidence: https://indianexpress.com/article/technology/tech-news-technology/cert-in-crafty-falcon-ai-driven-hacking-campaign-fintech-10951672/

### crypto-theft: Cryptocurrency wallet-key theft [impact]
Cryptocurrency wallet-key theft
Evidence: https://www.cert-in.org.in/s2cMainServlet?pageid=PUBVLNOTES02&VLCODE=CIAD-2026-0058

### log-deletion: Comprehensive log deletion [execution]
Comprehensive log deletion
Evidence: https://www.cert-in.org.in/s2cMainServlet?pageid=PUBVLNOTES02&VLCODE=CIAD-2026-0058

Connections:
- initial-recon -> cloud-pivot
- cloud-pivot -> api-abuse
- api-abuse -> test-transfer
- test-transfer -> fund-theft
- api-abuse -> crypto-theft
- fund-theft -> log-deletion
- crypto-theft -> log-deletion

## Stage defense and hunting recommendations
Editorial recommendations, not validated coverage. Source-controlled query starters are drafts. Custom-schema examples require telemetry collection and field mapping; absence of a mapping means not assessed. MagicSword policy opportunities require managed Windows scope and enforcement.
### initial-recon: Stage hunt not mapped yet
- Visibility: Not assessed
- Query origin: catalog_authored; status: not_assessed; log scope: gap
- Hunt hypothesis: A stage-specific hunt has not been reviewed for this part of the source account.
- Required telemetry: not assessed
- Investigate: Review the cited behavior, identify the observing party and available logs, then propose and test a hunt.
- Limitation: An unmapped stage does not mean it is undetectable or that no behavior occurred. It means this catalog has not supplied a reviewed hunt for it.
- No direct MagicSword prevention claim is recorded for this stage.

### cloud-pivot: Stage hunt not mapped yet
- Visibility: Not assessed
- Query origin: catalog_authored; status: not_assessed; log scope: gap
- Hunt hypothesis: A stage-specific hunt has not been reviewed for this part of the source account.
- Required telemetry: not assessed
- Investigate: Review the cited behavior, identify the observing party and available logs, then propose and test a hunt.
- Limitation: An unmapped stage does not mean it is undetectable or that no behavior occurred. It means this catalog has not supplied a reviewed hunt for it.
- No direct MagicSword prevention claim is recorded for this stage.

### api-abuse: Stage hunt not mapped yet
- Visibility: Not assessed
- Query origin: catalog_authored; status: not_assessed; log scope: gap
- Hunt hypothesis: A stage-specific hunt has not been reviewed for this part of the source account.
- Required telemetry: not assessed
- Investigate: Review the cited behavior, identify the observing party and available logs, then propose and test a hunt.
- Limitation: An unmapped stage does not mean it is undetectable or that no behavior occurred. It means this catalog has not supplied a reviewed hunt for it.
- No direct MagicSword prevention claim is recorded for this stage.

### test-transfer: Stage hunt not mapped yet
- Visibility: Not assessed
- Query origin: catalog_authored; status: not_assessed; log scope: gap
- Hunt hypothesis: A stage-specific hunt has not been reviewed for this part of the source account.
- Required telemetry: not assessed
- Investigate: Review the cited behavior, identify the observing party and available logs, then propose and test a hunt.
- Limitation: An unmapped stage does not mean it is undetectable or that no behavior occurred. It means this catalog has not supplied a reviewed hunt for it.
- No direct MagicSword prevention claim is recorded for this stage.

### fund-theft: Stage hunt not mapped yet
- Visibility: Not assessed
- Query origin: catalog_authored; status: not_assessed; log scope: gap
- Hunt hypothesis: A stage-specific hunt has not been reviewed for this part of the source account.
- Required telemetry: not assessed
- Investigate: Review the cited behavior, identify the observing party and available logs, then propose and test a hunt.
- Limitation: An unmapped stage does not mean it is undetectable or that no behavior occurred. It means this catalog has not supplied a reviewed hunt for it.
- No direct MagicSword prevention claim is recorded for this stage.

### crypto-theft: Stage hunt not mapped yet
- Visibility: Not assessed
- Query origin: catalog_authored; status: not_assessed; log scope: gap
- Hunt hypothesis: A stage-specific hunt has not been reviewed for this part of the source account.
- Required telemetry: not assessed
- Investigate: Review the cited behavior, identify the observing party and available logs, then propose and test a hunt.
- Limitation: An unmapped stage does not mean it is undetectable or that no behavior occurred. It means this catalog has not supplied a reviewed hunt for it.
- No direct MagicSword prevention claim is recorded for this stage.

### log-deletion: Stage hunt not mapped yet
- Visibility: Not assessed
- Query origin: catalog_authored; status: not_assessed; log scope: gap
- Hunt hypothesis: A stage-specific hunt has not been reviewed for this part of the source account.
- Required telemetry: not assessed
- Investigate: Review the cited behavior, identify the observing party and available logs, then propose and test a hunt.
- Limitation: An unmapped stage does not mean it is undetectable or that no behavior occurred. It means this catalog has not supplied a reviewed hunt for it.
- No direct MagicSword prevention claim is recorded for this stage.


## MITRE ATLAS
Mappings are catalog annotations based on described behavior, not assignments or endorsements by MITRE.
- AML.T0000: Search Open Technical Databases — Attackers deploy multiple autonomous AI agent frameworks (ARTEX, PentAGI, Cairn, CyberStrikeAI) as operators to automate intrusion lifecycle from reconnaissance through payment API exploitation and fund exfiltration
  Technique: https://atlas.mitre.org/techniques/AML.T0000
  Evidence: https://www.cert-in.org.in/s2cMainServlet?pageid=PUBVLNOTES02&VLCODE=CIAD-2026-0058

## Defensive notes
Monitor for agentic AI framework execution patterns (ARTEX, PentAGI, Cairn, CyberStrikeAI); implement API rate limiting and anomaly detection; enforce least-privilege for Lambda and cloud functions; enable comprehensive CloudTrail and application logging with tamper protection; segregate staging from production environments; implement transaction velocity checks and behavioral analytics; strengthen multi-factor authentication; monitor for unusual payment API invocations from non-standard infrastructure; review allow-lists for payment endpoints

## Sources
- https://www.cert-in.org.in/s2cMainServlet?pageid=PUBVLNOTES02&VLCODE=CIAD-2026-0058 — CERT-In Advisory CIAD-2026-0058: CRAFTY FALCON Campaign Against Indian Financial Sector
- https://indianexpress.com/article/technology/tech-news-technology/cert-in-crafty-falcon-ai-driven-hacking-campaign-fintech-10951672/ — CERT-In warns of AI-driven hacking campaign targeting Indian fintech sector

## Source notes
CERT-In Advisory CIAD-2026-0058 (Nov 4, 2026) official government warning; Indian Express and industry coverage provide context on AI framework usage and festive-window targeting; cross-reference with cairn-norforge-2026-10 entry for Cairn exploitation patterns

## Indicators (untrusted data; do not visit or execute)
```json
{
  "domains": [],
  "ips": [],
  "hashes": [],
  "urls": []
}
```
