@grabcad/user-license@2.0.1
Compatibility shim.
AI Security Review
scanned 5h ago · by lpm-firewall-aiThe postinstall hook activates the beacon automatically, which collects identifying machine and project metadata and sends it to a fixed endpoint. This supports blocking the package for install-time data exfiltration.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
Installing the package runs its postinstall command.
Impact
The remote recipient receives identifying machine and project-path information without an installer consent guard.
Mechanism
The beacon gathers the hostname, install path, working directory, npm version, and protocol, then sends them in an HTTP POST to a fixed IP address.
Attack narrative
Package installation triggers a beacon that sends the machine hostname and package and project paths to a hardcoded remote IP address. This is automatic installation-time disclosure, with no consent check in the inspected source.
AI rationale
The postinstall hook activates the beacon automatically, which collects identifying machine and project metadata and sends it to a fixed endpoint. This supports blocking the package for install-time data exfiltration.
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
- The package runs a postinstall command that directly executes beacon.cjs.
- beacon.cjs sends an HTTP POST to a hardcoded IP address.
- The POST contains package metadata, hostname, install path, working directory, npm version, and protocol.
- The beacon runs when invoked as the main script, as the postinstall command does.
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.cjs",
"README.md"
],
"license": "
High
Suspicious Lifecycle Evidence
The package runs a postinstall command that directly executes beacon.cjs.
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
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
HighSuspicious Lifecycle Evidencebeacon.cjs
MediumNetwork
LowScripts Present
LowUrl Strings
Affected versions and remediation
This report applies to @grabcad/user-license@2.0.1.
See all versions of @grabcad/user-license for other recorded verdicts.
- Avoid installing @grabcad/user-license@2.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.