registry / @atlasauth/embed / 0.2.1
@atlasauth/embed@0.2.1
AI Security Review
scanned 21d ago · by lpm-firewall-aiSource inspection found no malicious behavior. Authentication submissions go through the configured frontend API, and the bundled telemetry is consistent with device and bot-detection reporting.
Static reason
No blocking static signals were detected.
Trigger
Widget mount starts interaction recording; sign-in, registration, or provider actions trigger authentication requests and telemetry.
Impact
The inspected behavior supports the package’s authentication widget and bot-detection telemetry; no unauthorized account change or unrelated credential recipient was established.
Mechanism
The widget sends entered authentication data through its configured API client. Telemetry contains device characteristics and aggregate interaction metrics; no inspected telemetry payload includes form values.
AI rationale
Source inspection found no malicious behavior. Authentication submissions go through the configured frontend API, and the bundled telemetry is consistent with device and bot-detection reporting.
Network endpoints1
accounts.google.com/gsi/client
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest points to the widget module and declares only build, typecheck, and test scripts; it has no install lifecycle hook.
- The inspected authentication callers submit form, social-provider, reset, and passkey data through the widget’s configured frontend API.
- The bundled recorder gathers device details and aggregate interaction metrics, then sends telemetry to the configured frontend API; the inspected telemetry payload does not include form values.
Evidence against
Behavioral surface
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
8 flaggeddist/embed.jsView file
1"use strict";(()=>{var ho=Object.create;var Ve=Object.defineProperty;var yo=Object.getOwnPropertyDescriptor;var ko=Object.getOwnPropertyNames;var vo=Object.getPrototypeOf,xo=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 unpkgpackage.jsonView 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
LowSuspicious Lifecycle Evidencepackage.json
LowSuspicious Lifecycle Evidencepackage.json
LowAi Review Evidencedist/widget/render.js
LowAi Review Evidencedist/widget/render.js
LowAi Review Evidencedist/widget/render.js
LowAi Review Evidencedist/widget/render.js
Affected versions and remediation
This report applies to @atlasauth/embed@0.2.1.
See all versions of @atlasauth/embed for other recorded verdicts.
- Review the evidence and your use of @atlasauth/embed@0.2.1 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.