registry / @atlasauth/embed / 0.3.0
@atlasauth/embed@0.3.0
AI Security Review
scanned 20d ago · by lpm-firewall-aiThe manifest has no install hook, and inspected runtime callers use the configured API for interactive authentication and recovery flows. Telemetry sends device and aggregate interaction measurements; the inspected source does not show credential forwarding to an unrelated recipient or account-setting mutation.
Static reason
No blocking static signals were detected.
Trigger
A consumer imports or mounts the widget; authentication, reset, and sign-up actions run when a user interacts with its controls.
Impact
No disclosure to an unrelated recipient or unsolicited account change was identified; the observed requests support the widget’s authentication flows.
Mechanism
Authentication requests use the configured API base URL. Form submissions also send device and aggregate interaction telemetry to that API.
AI rationale
The manifest has no install hook, and inspected runtime callers use the configured API for interactive authentication and recovery flows. Telemetry sends device and aggregate interaction measurements; the inspected source does not show credential forwarding to an unrelated recipient or account-setting mutation.
Network endpoints3
/v1/client/telemetry/v1/client/sign_ins/passkey/begin/v1/client/sign_ins/passkey/finish
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes the module entry and lists build, typecheck, and test scripts, with no install lifecycle hook.
- The API client sends requests to the configured base URL, including browser credentials; the inspected callers use it for widget authentication flows.
- The cited runtime locations resolve to interactive sign-in, passkey, social login, password reset, sign-up, and rendering handlers; no unrelated account mutation was identified.
- Form-submission telemetry goes to the configured API and carries device and aggregate interaction measurements; the inspected payload does not include form values.
Evidence against
- The widget sends device and interaction telemetry during form submissions, and its configured API requests include browser credentials.
Behavioral surface
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
8 flaggeddist/embed.jsView file
1"use strict";(()=>{var xo=Object.create;var tt=Object.defineProperty;var wo=Object.getOwnPropertyDescriptor;var So=Object.getOwnPropertyNames;var _o=Object.getPrototypeOf,Eo=Object...
L2: .atlas-embed-root {
High
Browser Session Account Hijack
Browser source reuses an authenticated session to collect identity data and mutate account settings while reporting externally.
dist/embed.jsView on unpkg · L1dist/widget/social.js#virtual:normalized:round1View file
•stage = ast_semantic_analysis; reason = ast_parse_error; limitedFiles = 1
High
Semantic Analysis Limited
A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
dist/widget/social.js#virtual:normalized:round1View on unpkgdist/widget/passkey.jsView file
Findings
2 High10 Low
HighBrowser Session Account Hijackdist/embed.js
HighSemantic Analysis Limiteddist/widget/social.js#virtual:normalized:round1
LowScripts Present
LowHigh Entropy Strings
LowUrl Strings
LowNo License
LowAi Review Evidencedist/widget/passkey.js
LowAi Review Evidencedist/widget/passkey.js
LowAi Review Evidencedist/widget/social.js
LowAi Review Evidencedist/widget/render.js
LowAi Review Evidencedist/widget.js
LowAi Review Evidencedist/widget/render.js
Affected versions and remediation
This report applies to @atlasauth/embed@0.3.0.
See all versions of @atlasauth/embed for other recorded verdicts.
- Review the evidence and your use of @atlasauth/embed@0.3.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.