REST Studio — REST & API Client, HTTP Requests & API Testing

AI Security Review

Evidence context: threat category none; evidence quality moderate.

The extension's stated job is a REST/API client for VS Code-family editors: it keeps collections as files in your repo and sends HTTP requests. Filesystem and process access on that basis is expected. No finding here shows the extension reading source files you did not point it at, and no finding shows it spawning a shell.

The one high-severity alert is OBfuscation-UNICODE_HEAVY-extension/out/extension.js-161, raised against extension/out/extension.js line 161. That path is the compiled bundle of the TypeScript source. Heavy non-ASCII character density in a bundle comes from minified library code, embedded UI glyphs and localized strings. Treating a bundled build file as deliberate obfuscation is a known false positive; the source lives on the project's repository.

On credentials, the evidence is quiet. Nothing appears in the secret category, nothing touches .env, .ssh, .git/config or cloud credential files, and the manifest declares no permissions and no host permissions. The broad API-key and environment-variable patterns that fire on any non-trivial JavaScript did not surface a real secret read.

Network endpoints read the way a REST client's endpoints should. schema.getpostman.com is Postman's collection schema, needed to import Postman collections. schemas.openxmlformats.org is the Office Open XML namespace used when handling document formats. mantine.dev is the React component library behind the webview panel. img.shields.io serves the README badges. api.northwind-goods.com is a sample endpoint matching the demo collection a REST client ships for test requests. Several entries are not hosts at all: body.total, btn.icon.sm, cn.show, d6r.kh, kv.no, p8.bo and qt.group are property-access chains and fragments the extractor misread as domains.

Two endpoints do belong to the developer. ciromaciel.click and by-ciromaciel.click match the publisher name ciro-maciel and look like the project site and update host. That is the strongest counterargument to calling this clean. An extension sending workspace contents to a personal domain would be exfiltration. Here nothing pairs a workspace read with those hosts, they sit alongside a demo API and library schemas, and a client that talks to its own site for updates is unremarkable.

The low-severity code-smell matches are the generic Node.js fetch, exec, crypto and API-key rules that fire on any bundled JavaScript, and they carry no behavioral weight. No malware signature, tool-poisoning or manifest-analysis finding appears. The picture is a small, low-download extension whose findings come from bundled build output and hostname-extraction noise, not from observed malicious behavior.

Key Reasons

• Only high-severity finding is OBfuscation-UNICODE_HEAVY-extension/out/extension.js-161 in compiled build output, a known false positive on bundled code
• No secret, malware-signature, tool-poisoning or manifest-analysis findings; no .env, .ssh or credential-provider access
• Network endpoints (schema.getpostman.com, mantine.dev, img.shields.io, api.northwind-goods.com) fit a REST client's Postman import and webview stack
• Developer domain ciromaciel.click matches publisher name ciro-maciel and is not paired with any workspace read
• Code-smell and IoC findings are broad Node.js patterns and misparsed property-access chains, not behavioral evidence

False Positive Considerations

• IoC extractor misread property-access chains (body.total, btn.icon.sm, cn.show, d6r.kh, kv.no, p8.bo, qt.group) as hostnames
• UNICODE_HEAVY obfuscation rule firing on the compiled out/extension.js bundle
• Code-smell rules matching generic Node.js fetch/exec/crypto and API-key patterns
• Bundled webview libraries (Mantine) and demo API endpoint producing expected network strings

Reviewed 2026-10-17; recommended action: suppress false positive; model confidence 82%.