registry / @wraps.dev/cli / 3.18.0
@wraps.dev/cli@3.18.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 6d ago · by lpm-firewall-aiThe package is an AWS deployment CLI with no install lifecycle scripts. Its telemetry is disclosed, limited in the inspected event construction, and can be disabled; the flagged credential and shell references did not establish malicious behavior.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
AWS identity validation occurs when a relevant command requests it; telemetry is emitted during CLI command use.
Impact
No malicious credential transfer or unrelated automatic action was established. Telemetry is disclosed and can be disabled.
Mechanism
AWS credentials are used with AWS STS. Telemetry sends command events and runtime metadata to the Wraps telemetry endpoint, with opt-out controls.
AI rationale
The package is an AWS deployment CLI with no install lifecycle scripts. Its telemetry is disclosed, limited in the inspected event construction, and can be disabled; the flagged credential and shell references did not establish malicious behavior.
Evidence
dist/cli.jspackage.json
Network endpoints2
wraps.dev/api/telemetryAWS STS endpoint selected by the AWS SDK
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes dist/cli.js as the CLI entry point and defines no install lifecycle scripts.
- AWS credential handling uses configured credentials to validate identity through AWS STS, consistent with the package’s AWS deployment purpose.
- Runtime telemetry records command events with CLI version, platform, Node version, CI status, and an anonymous ID.
- The CLI discloses telemetry and provides a command and environment variable to disable it.
Evidence against
- The CLI reads AWS credential configuration and environment variables, but the inspected flows use these to detect or validate AWS credentials.
- The scanner flagged metadata addresses and shell commands, but the inspected references were AWS SDK code and displayed installation guidance; no unrelated credential receiver or automatic download-and-run behavior was established.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
Source & flagged code
14 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
3 Critical7 High5 Medium8 Low
CriticalHardcoded Runtime Data Exfiltrationdist/cli.js
CriticalTrigger Reachable Dangerous Capabilitydist/cli.js
CriticalPrevious Version Dangerous Deltadist/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
Affected versions and remediation
This report applies to @wraps.dev/cli@3.18.0.
See all versions of @wraps.dev/cli for other recorded verdicts.
- Review the evidence and your use of @wraps.dev/cli@3.18.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.