@grabcad/user-license@3.0.0
Compatibility shim.
AI Security Review
scanned 5h ago · by lpm-firewall-aiThe manifest activates the beacon automatically during installation, and the source constructs and sends a payload containing host and install identifiers to a hardcoded external endpoint. This is unconsented installation-time disclosure of identifying metadata.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
Package installation runs the postinstall command; directly running beacon.cjs also activates the report.
Impact
The endpoint receives identifying installation and machine metadata without an affirmative opt-in.
Mechanism
The beacon collects the hostname, install path, working directory, and npm version, then sends them in a POST request.
Attack narrative
Installing the package runs its postinstall beacon. The beacon sends the machine hostname, installation path, working directory, and npm version to a hardcoded external IP address without an affirmative consent check.
AI rationale
The manifest activates the beacon automatically during installation, and the source constructs and sends a payload containing host and install identifiers to a hardcoded external endpoint. This is unconsented installation-time disclosure of identifying metadata.
Evidence
package.jsonbeacon.cjs
Network endpoints1
185.158.107.175:8787/_ah/dc
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- package.json runs beacon.cjs automatically during postinstall.
- beacon.cjs sends a POST to a hardcoded external IP address.
- The request payload includes the machine hostname, install path, working directory, and npm version.
- Running beacon.cjs directly calls fire without a consent check.
Evidence against
Behavioral surface
Network
UrlStrings
Source & flagged code
7 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node beacon.cjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg7"postinstall": "node beacon.cjs"
},
"files": [
"index.js",
"beacon.c
High
Suspicious Lifecycle Evidence
package.json runs beacon.cjs automatically during postinstall.
package.jsonView on unpkg · L7beacon.cjsView file
•matchType = malicious_source_fingerprint_signature
signature = a5258e167635ba3a
signatureType = suspicious_hashes
sourceLabel = final_verdict:malicious
matchedPackage = @blueskydataplatform/shared-ui@99.0.3
matchedPath = beacon.cjs
matchedIdentity = npm:[redacted]:99.0.3
similarity = 1.000
shingleOverlap = 2
summary = package final verdict is malicious
High
Known Malware Source Fingerprint Signature
Source fingerprint signature matches a known malicious package signature; route for source-aware review.
Findings
7 High1 Medium2 Low
HighInstall Time Lifecycle Scriptspackage.json
HighKnown Malware Source Fingerprint Signaturebeacon.cjs
HighSuspicious Lifecycle Evidencepackage.json
HighAi Review Evidencebeacon.cjs
HighAi Review Evidencebeacon.cjs
HighAi Review Evidencebeacon.cjs
HighAi Review Evidencebeacon.cjs
MediumNetwork
LowScripts Present
LowUrl Strings
Affected versions and remediation
This report applies to @grabcad/user-license@3.0.0.
See all versions of @grabcad/user-license for other recorded verdicts.
- Avoid installing @grabcad/user-license@3.0.0. 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.