@grabcad/user-license@1.0.1
Compatibility shim.
AI Security Review
scanned 2h ago · by lpm-firewall-aiSource inspection confirms automatic disclosure of identifying install metadata to a fixed external collector during installation, with an additional import-time trigger. This meets the installation beacon policy for blocking.
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 hook; importing the package also invokes the beacon.
Impact
The endpoint receives identifying information about the machine and package installation.
Mechanism
The beacon posts the hostname, installation path, working directory, and runtime version to the configured endpoint without a consent gate.
Attack narrative
The postinstall hook launches a beacon that sends machine and installation identifiers to a fixed external endpoint. The library entrypoint also invokes the same beacon when imported. The inspected activation paths contain no affirmative consent gate.
AI rationale
Source inspection confirms automatic disclosure of identifying install metadata to a fixed external collector during installation, with an additional import-time trigger. This meets the installation beacon policy for blocking.
Evidence
package.jsonbeacon.cjsindex.js
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 the beacon automatically during postinstall.
- beacon.cjs sends an HTTP POST to a fixed external IP address.
- The beacon payload includes the machine hostname, installation path, working directory, and runtime version.
- Importing index.js also calls the beacon helper.
Evidence against
Behavioral surface
Network
UrlStrings
Source & flagged code
8 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.cjs",
"
High
Suspicious Lifecycle Evidence
package.json runs the beacon 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@2.0.0
matchedPath = beacon.cjs
matchedIdentity = npm:[redacted]:2.0.0
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
8 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
HighAi Review Evidenceindex.js
MediumNetwork
LowScripts Present
LowUrl Strings
Affected versions and remediation
This report applies to @grabcad/user-license@1.0.1.
See all versions of @grabcad/user-license for other recorded verdicts.
- Avoid installing @grabcad/user-license@1.0.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.