@wraps.dev/cli@3.19.0
Deploy email, SMS, and CDN infrastructure to your AWS account with one command. Sets up SES with DKIM/SPF/DMARC, event processing, and history automatically.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe source shows disclosed, opt-out runtime telemetry, but deployment configuration fields exceed the notice’s stated collection. This warrants a warning; the reviewed source does not establish credential theft or another blocking attack.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user runs a CLI command that records service initialization or deployment telemetry.
Impact
The vendor receives deployment configuration and usage details that the notice says it does not collect; no credential or domain exfiltration was identified.
Mechanism
The CLI attaches values such as preset, provider, and AWS region to telemetry events and posts them to the Wraps telemetry endpoint.
AI rationale
The source shows disclosed, opt-out runtime telemetry, but deployment configuration fields exceed the notice’s stated collection. This warrants a warning; the reviewed source does not establish credential theft or another blocking attack.
Evidence
dist/cli.js
Network endpoints1
wraps.dev/api/telemetry
Decision evidence
public snapshotAI called this Suspicious at 94.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The first-run notice says telemetry collects only command names, success or failure, CLI version, and OS, and offers an opt-out.
- Telemetry also sends deployment metadata including the selected preset, provider, and AWS region.
- Telemetry is enabled by default and posts events to https://wraps.dev/api/telemetry unless disabled by configuration or environment settings.
- The CLI sends telemetry while handling user-run commands; no install-time hook was found.
Evidence against
- The manifest describes a CLI for deploying email, SMS, and CDN infrastructure to AWS, which explains its AWS credential and SDK use.
- The source says it does not collect domains, AWS credentials, email content, or PII; no forwarding of credentials to an unrelated host was identified.
- The detected shell download match is an installation help string, while the updater asks for confirmation and retrieves release assets from GitHub.
- The manifest has no preinstall, install, or postinstall lifecycle scripts.
Behavioral surface
ChildProcess
Source & flagged code
13 flaggeddist/cli.jsView file
19import { fileURLToPath } from "url";
L20: var getFilename, getDirname, __dirname;
L21: var init_esm_shims = __esm({
...
L272: // src/utils/shared/aws-detection.ts
L273: import { execSync } from "child_process";
L274: import { existsSync, readdirSync, readFileSync } from "fs";
...
L295: function detectCredentialSource() {
L296: if (process.env.AWS_ACCESS_KEY_ID && process.env.AWS_SECRET_ACCESS_KEY) {
L297: return "environment";
...
L338: const sts = new STSClient({ region: "us-east-1" });
L339: const identity = await sts.send(new GetCallerIdentityCommand({}));
L340: return identity.Account || null;
Critical
Hardcoded Runtime Data Exfiltration
Source sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/cli.jsView on unpkg · L1919Trigger-reachable chain: manifest.main -> dist/cli.js
L19: import { fileURLToPath } from "url";
L20: var getFilename, getDirname, __dirname;
L21: var init_esm_shims = __esm({
...
L272: // src/utils/shared/aws-detection.ts
L273: import { execSync } from "child_process";
L274: import { existsSync, readdirSync, readFileSync } from "fs";
...
L295: function detectCredentialSource() {
L296: if (process.env.AWS_ACCESS_KEY_ID && process.env.AWS_SECRET_ACCESS_KEY) {
L297: return "environment";
...
L338: const sts = new STSClient({ region: "us-east-1" });
L339: const identity = await sts.send(new GetCallerIdentityCommand({}));
L340: return identity.Account || null;
Critical
Trigger Reachable Dangerous Capability
A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
Findings
2 Critical7 High5 Medium8 Low
CriticalHardcoded Runtime Data Exfiltrationdist/cli.js
CriticalTrigger Reachable Dangerous Capabilitydist/cli.js
HighChild Processdist/cli.js
HighShelldist/cli.js
HighCredential Redirect Persistencedist/cli.js
HighSandbox Evasion Gated Capabilitydist/cli.js
HighCloud Metadata Accessdist/cli.js
HighCross File Remote Execution Contextdist/cli.js
HighSemantic Analysis Limiteddist/lambda/inbound-processor/index.js
MediumDynamic Requiredist/lambda/agent-enforcer/index.js
MediumNetwork
MediumEnvironment Vars
Medium
Affected versions and remediation
This report applies to @wraps.dev/cli@3.19.0.
See all versions of @wraps.dev/cli for other recorded verdicts.
- Review the evidence and your use of @wraps.dev/cli@3.19.0 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.