mlsanityData to 14 Oct 2026

The Midas Touch: Triggering the Capability of LLMs for RM-API Misuse Detection

arXiv 2409.09380 ↗First posted 14 Sep 2024cs.CRcited by 3

Not on the map. Why?

Abstract (arXiv)

In this paper, we propose an LLM-empowered RM-API misuse detection solution, ChatDetector, which fully automates LLMs for documentation understanding which helps RM-API constraints retrieval and RM-API misuse detection. To correctly retrieve the RM-API constraints, ChatDetector is inspired by the ReAct framework which is optimized based on Chain-of-Thought (CoT) to decompose the complex task into allocation APIs identification, RM-object (allocated/released by RM APIs) extraction and RM-APIs pairing (RM APIs usually exist in pairs). It first verifies the semantics of allocation APIs based on the retrieved RM sentences from API documentation through LLMs. Inspired by the LLMs' performance on various prompting methods,ChatDetector adopts a two-dimensional prompting approach for cross-validation. At the same time, an inconsistency-checking approach between the LLMs' output and the reasoning process is adopted for the allocation APIs confirmation with an off-the-shelf Natural Language Processing (NLP) tool. To accurately pair the RM-APIs, ChatDetector decomposes the task again and identifies the RM-object type first, with which it can then accurately pair the releasing APIs and further construct the RM-API constraints for misuse detection. With the diminished hallucinations, ChatDetector identifies 165 pairs of RM-APIs with a precision of 98.21% compared with the state-of-the-art API detectors. By employing a static detector CodeQL, we ethically report 115 security bugs on the applications integrating on six popular libraries to the developers, which may result in severe issues, such as Denial-of-Services (DoS) and memory corruption. Compared with the end-to-end benchmark method, the result shows that ChatDetector can retrieve at least 47% more RM sentences and 80.85% more RM-API constraints.

Key facts. Cited by 3 papers in the map (data through 14 Oct 2026). First posted on arXiv 14 Sep 2024.

Builds on

No reference list yet.

Built on by

Cited by year (2026 to 14 Oct)

Citing papers per year: 2025: 1; 2026: 2.

3 papers.

Similar, not cited

Close in wording, no citation either way

  1. 2024Harnessing LLMs for API Interactions: A Framework for Classification and Synthetic Data Generation
  2. 2024Octopus: On-device language model for function calling of software APIs
  3. 2025Evaluating LLMs on Sequential API Call Through Automated Test Generation
  4. 2026Mitigating Errors in LLM-Generated Web API Invocations via Retrieval-Augmented Generation and Constrained Decoding
  5. 2023API-Bank: A Comprehensive Benchmark for Tool-Augmented LLMs
  6. 2025Towards Mitigating API Hallucination in Code Generated by LLMs with Hierarchical Dependency Aware
  7. 2026Prompt Control-Flow Integrity: A Priority-Aware Runtime Defense Against Prompt Injection in LLM Systems
  8. 2025CallNavi, A Challenge and Empirical Study on LLM Function Calling and Routing