registry / @atlasauth/embed / 0.6.0
@atlasauth/embed@0.6.0
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe flagged credential references are part of the widget’s authentication and recovery flows, and the shared client targets the configured frontend API. The manifest has no install hook, and the inspected runtime behavior establishes no unrelated recipient or account action.
Static reason
No blocking static signals were detected.
Trigger
A user submits an authentication form or selects a sign-in option.
Impact
No unrelated credential transfer or other concrete attack behavior was established.
Mechanism
The widget sends authentication requests to its configured frontend API; social sign-in begins from a user click and uses matching OAuth messages for coordination.
AI rationale
The flagged credential references are part of the widget’s authentication and recovery flows, and the shared client targets the configured frontend API. The manifest has no install hook, and the inspected runtime behavior establishes no unrelated recipient or account action.
Evidence
package.jsondist/embed.jsdist/widget/social.js
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json declares only build, typecheck, and test scripts; no install lifecycle hook is present.
- The shared HTTP client sends requests to its configured frontend API and includes browser credentials, consistent with the widget’s authentication role.
- Flagged bundle locations are in signup, sign-in, recovery, OAuth, passkey, and form handling paths; they show no unrelated credential recipient.
- The social sign-in starts on a button click, and the message listener accepts only a matching Atlas OAuth acknowledgment.
Evidence against
Behavioral surface
Network
HighEntropyStringsPossibleObfuscationUrlStrings
NoLicense
Source & flagged code
7 flaggeddist/embed.jsView file
1"use strict";(()=>{var so=Object.create;var ot=Object.defineProperty;var io=Object.getOwnPropertyDescriptor;var lo=Object.getOwnPropertyNames;var co=Object.getPrototypeOf,uo=Object...
L2: self.onmessage = async function (e) {
...
L381: @keyframes atlas-embed-pulse { 0%,100% { opacity: 0.4; } 50% { opacity: 1; } }
L382: `;function Tr(e=document){var n;if(e.querySelector(`style[data-${Cr}]`))return;let t=e.createElement("style");t.setAttribute(`data-${Cr}`,""),t.textContent=Na,((n=e.head)!=null?n:e...
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 · L11e.post("/v1/client/sign_ups",{email:t.email,password:t.password,...n?{fields:t.fields}:{},...t.consent?{consent:!0}:{},...t.captchaToken?{captcha_token:t.captchaToken}:{}});return!
Low
Ai Review Evidence
Flagged bundle locations are in signup, sign-in, recovery, OAuth, passkey, and form handling paths; they show no unrelated credential recipient.
dist/embed.jsView on unpkg · L1382lt(e.client,{email:r!=null?r:"",password:o!=null?o:"",fields:s,consent:n,captchaToken:l!=null?l:void 0}),e.busy=!1;let i=e.state.attempt;if((i==null?void 0:i.status)==="complete"){
Findings
2 High1 Medium9 Low
HighBrowser Session Account Hijackdist/embed.js
HighSemantic Analysis Limiteddist/widget/social.js#virtual:normalized:round1
MediumNetwork
LowScripts Present
LowHigh Entropy Strings
LowUrl Strings
LowNo License
LowSuspicious Lifecycle Evidencepackage.json
LowAi Review Evidencedist/embed.js
LowAi Review Evidencedist/embed.js
LowAi Review Evidencedist/embed.js
LowAi Review Evidencedist/embed.js
Affected versions and remediation
This report applies to @atlasauth/embed@0.6.0.
See all versions of @atlasauth/embed for other recorded verdicts.
- Review the evidence and your use of @atlasauth/embed@0.6.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.