registry / @atlassecurity/auth / 1.1.2
@atlassecurity/auth@1.1.2
Atlas SDK - Node.js binding for Atlas.dll (Windows x64).
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe inspected lifecycle hook performs a limited SDK marker write, and the JavaScript entrypoint uses the bundled DLL as a native SDK binding. These behaviors align with the package's stated purpose, and no concrete malicious behavior was established.
Static reason
One or more suspicious static signals were detected.
Trigger
The marker write runs during npm postinstall; DLL loading occurs when the entrypoint is imported.
Impact
The inspected behavior records local SDK installation state and provides native SDK functions; no malicious effect was established.
Mechanism
The hook records the SDK name, version, and timestamp in the user's local application data directory. The JavaScript entrypoint loads Atlas.dll using koffi.
AI rationale
The inspected lifecycle hook performs a limited SDK marker write, and the JavaScript entrypoint uses the bundled DLL as a native SDK binding. These behaviors align with the package's stated purpose, and no concrete malicious behavior was established.
Evidence
postinstall.jssrc/index.jspackage.json
Decision evidence
public snapshotAI called this Clean at 89.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The install hook creates an Atlas SDK marker under the user's local application data directory.
- The entrypoint loads the bundled DLL through the native binding; this matches the package's stated Windows SDK role.
- The JavaScript exposes webhook operations that callers invoke with supplied endpoint and message arguments.
Evidence against
- No concrete malicious behavior was identified in the inspected lifecycle hook or JavaScript entrypoint.
Behavioral surface
CryptoEnvironmentVarsFilesystem
HighEntropyStrings
NoLicense
Source & flagged code
6 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node postinstall.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node postinstall.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkg16"scripts": {
"postinstall": "node postinstall.js"
}
Low
Suspicious Lifecycle Evidence
The install hook creates an Atlas SDK marker under the user's local application data directory.
package.jsonView on unpkg · L16Atlas.dllView file
Findings
1 High4 Medium7 Low
HighInstall Time Lifecycle Scriptspackage.json
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumEnvironment Vars
MediumShips Native BinaryAtlas.dll
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowNo License
LowSuspicious Lifecycle Evidencepackage.json
LowSuspicious Lifecycle Evidencepostinstall.js
LowAi Review Evidencesrc/index.js
Affected versions and remediation
This report applies to @atlassecurity/auth@1.1.2.
See all versions of @atlassecurity/auth for other recorded verdicts.
- Review the evidence and your use of @atlassecurity/auth@1.1.2 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.