Last updated: 13 November 2026. You will find the sources at the end.

Crafty Falcon is the name CERT-In has given to a group that is stealing money from Indian lenders and payment companies through their own payment APIs. The warning came on 4 November 2026 from CSIRT-Fin, the finance arm of CERT-In, as an update to an advisory from 9 October. CERT-In calls the campaign active and ongoing, and says companies that had already been hit were attacked again after incomplete fixes.

The targets are smaller than the banks that usually make the news: NBFCs, digital lending apps, fintechs, payment aggregators, payment service providers and crypto exchanges. If your company moves money through an API, this guide turns the advisory into ten checks you can start on this week.

The short answer

  • The attackers get in through test and staging systems that are open to the internet, then move to production with shared passwords, tokens or network paths.
  • They call the company’s own disbursement and settlement APIs. A transfer of about ₹1 comes first to see whether the path works, and the large transfers follow.
  • They work on weekends, holidays and at night, when fewer people are watching.
  • They use AI tools to study each target and rewrite their attack scripts quickly, and they change IP addresses within hours or days. Blocklists alone will not stop them.
  • CERT-In says to treat this as “an immediate and continuing threat”.

What CERT-In says Crafty Falcon does

This list follows the public CERT-In note (CICA-2026-3651, which points to advisory CIAD-2026-0058). The technical indicators went only to regulated financial companies in a restricted version.

StepWhat CERT-In describes
Way inInternet-exposed UAT, staging and testing environments
Move to productionShared credentials, tokens or network paths between test and live systems
CloudAWS Systems Manager and Lambda used to run commands and place files, so the activity looks like normal administration
AppsMobile and web apps taken apart, and modified app packages used to make API calls the real app would not allow
IP allow-listsTraffic sent through third-party “fetcher” services whose IP ranges the victim had already allowed
Money₹1 test transfers, then large ones. Merchant settlement APIs at payment aggregators are also abused
New bugsFresh file-upload and deserialisation flaws used quickly to plant web shells in PHP and Node.js applications
ToolsAI-driven offensive tools. CERT-In names the ARTEX family, PentAGI, Cairn and CyberStrikeAI

Two points on that list catch companies that think they are covered. A test server often holds real API keys because someone needed “one quick test with live data”. An IP allow-list that includes a shared cloud service trusts every customer of that service.

Ten checks for this week

The checks below are our practical reading of the advisory and of the recommendations Infosecurity Magazine reported from it. None of them needs a new product.

  1. List every UAT, staging and test hostname you have and test each one from a phone on mobile data. Move anything that answers behind a VPN or switch it off.
  2. Compare secrets between test and production. API keys, database passwords and tokens must be different, and a test server should have no network route to production databases or payment services.
  3. Check that the server validates every transaction on its own. The API must enforce amount limits, beneficiary checks and KYC status. A check that exists only inside the mobile app does not count.
  4. Review every IP allow-list on your payment APIs. Remove ranges that belong to shared services such as link previewers, URL fetchers or generic cloud ranges. Signed requests or mutual TLS are stronger than an IP list.
  5. Add one transaction rule today: a very small transfer to a new beneficiary followed by a large transfer to the same beneficiary goes on hold for review. CERT-In describes exactly this pattern.
  6. Put limits on disbursement and settlement APIs: a daily cap per beneficiary, a cooling period for new beneficiaries and a second approver above a set amount.
  7. Restrict who can run remote commands and change serverless code in your cloud account, and alert on every use outside a planned change.
  8. Patch internet-facing PHP and Node.js applications within days, and watch web directories for new script files.
  9. Staff your monitoring for weekends and holidays. Decide now who gets the call at 2 am on a Sunday and what they may switch off.
  10. If you were hit before, finish the fix. Rotate every secret the attackers could have seen, rebuild affected servers and keep hunting. CERT-In notes that attackers targeted victims with incomplete fixes again.

Crypto exchanges have one more item from the advisory: the attackers steal wallet keys. Keep them in an HSM or in cold storage and require more than one person to approve a withdrawal.

A quick look at check 7 on AWS

These two AWS CLI commands list recent uses of Systems Manager Run Command and recent Lambda code changes from CloudTrail. They come from AWS documentation and we have not run them against a production account for this guide. Use them only in accounts you manage, and change the date.

aws cloudtrail lookup-events \
  --lookup-attributes AttributeKey=EventName,AttributeValue=SendCommand \
  --start-time 2026-11-01T00:00:00Z \
  --query 'Events[].{time:EventTime,user:Username,id:EventId}' --output table
aws cloudtrail lookup-events \
  --lookup-attributes AttributeKey=EventName,AttributeValue=UpdateFunctionCode20150331v2 \
  --start-time 2026-11-01T00:00:00Z \
  --query 'Events[].{time:EventTime,user:Username,id:EventId}' --output table

Every row should match a person and a change you know about. A run on a Saturday night by a role that normally does nothing is the thing to look into. lookup-events covers the last 90 days of management events in one region, so repeat it for each region you use.

Free tool: A forgotten test site is often visible from outside. Our website safety check grades what your main site shows to the internet in seconds.

Why small lenders are the target

A large bank has a fraud team awake all night. A lender with forty staff has two developers, one cloud account and a payment partner’s API key in a configuration file. The money that passes through is still real. CERT-In’s wording about “low-monitoring periods” describes this gap. The attackers have automated the slow part of the work, which is studying each target, and they now have time for the small ones.

Speed is the other change. Reports on the advisory say the tools generate and rework attack scripts for each target, and CERT-In itself says the infrastructure rotates within hours to days. A control that depends on a person noticing something on Monday morning comes too late. Checks 5 and 6 work without anyone being awake, which is why we would do them first.

If money has already moved

  • Call your bank and payment partner at once and ask them to hold the beneficiary accounts. The first hours decide how much comes back.
  • Report bulk fraudulent transactions to I4C through the National Cyber Crime Reporting Portal or the 1930 helpline.
  • Report the incident to CERT-In with logs. Under the CERT-In Directions of 28 April 2022 you have six hours from noticing it. Regulated entities also have their regulator’s reporting rules.
  • Keep the evidence. Do not wipe the test server that was the way in until you have saved the logs and a disk image.
  • Regulated financial companies can ask CERT-In for the restricted version of the advisory, which has the indicators.

Our guide to AI agents and leaked API keys covers the earlier CERT-In warning on the same theme, and what a web application VAPT covers explains how an outside test of your APIs is scoped.

Related guides

Sources

Want your payment APIs tested before someone else does it? Our VAPT services cover web, mobile and API testing with a fix-first report. Contact us for a quote.

Post author avatar

Bhaskar Soni

Bhaskar Soni is a Security Engineer and the founder of Youngster Company, based in Ahmedabad, Gujarat. He works hands-on with Linux server hardening, vulnerability assessment and penetration testing (VAPT), ISO 27001 compliance and OSINT investigations. He writes practical, tested guides for IT professionals and Indian businesses, and every article on this site is written or reviewed by him.

Leave a Reply