@inchurch/matcha-components@22.42.1
[Link to the project](https://bitbucket.org/inradar/design-system/src/master/).
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe PageBuilder’s confirmed canvas-clear action silently erases all localStorage for the site, including unrelated application data. This is hidden destructive behavior, so the package should be blocked.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user clicks the canvas-clear button and accepts the confirmation prompt.
Impact
Unrelated application state saved in localStorage for that origin is erased.
Mechanism
The handler clears the canvas and then calls localStorage.clear() without limiting deletion to PageBuilder data.
Attack narrative
When a user confirms clearing the PageBuilder canvas, the handler also clears every localStorage entry for the current origin. The confirmation describes only cleaning the canvas, so it does not disclose or authorize erasing unrelated application data.
AI rationale
The PageBuilder’s confirmed canvas-clear action silently erases all localStorage for the site, including unrelated application data. This is hidden destructive behavior, so the package should be blocked.
Evidence
fesm2022/inchurch-matcha-components.mjslocalStorage for the current browser origin
Decision evidence
public snapshotAI called this Malicious at 94.0% confidence as Malware with low false-positive risk.
Evidence for block
- The PageBuilder’s canvas-clear handler confirms only a canvas reset, then calls localStorage.clear(), erasing all browser storage for the current origin.
Evidence against
- The package exports a browser component bundle and declares no install or other lifecycle scripts.
- The destructive call is attached to a PageBuilder clear action that requires a user click and confirmation.
Behavioral surface
DynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsMinifiedPossibleObfuscationUrlStrings
NoLicense
Source & flagged code
5 flaggedassets/page-builder/js/grapesjs-plugin-export.jsView file
1/*! grapesjs-plugin-export - 1.0.11 */
L2: !function(e,t){'object'==typeof exports&&'object'==typeof module?module.exports=t():'function'==typeof define&&define.amd?define([],t):'object'==typeof exports?exports["grapesjs-pl...
L3: //# sourceMappingURL=index.js.map
Medium
Dynamic Require
Package source references dynamic require/import behavior.
assets/page-builder/js/grapesjs-plugin-export.jsView on unpkg · L11/*! grapesjs-plugin-export - 1.0.11 */
L2: !function(e,t){'object'==typeof exports&&'object'==typeof module?module.exports=t():'function'==typeof define&&define.amd?define([],t):'object'==typeof exports?exports["grapesjs-pl...
L3: //# sourceMappingURL=index.js.map
Low
Eval
Package source references a known benign dynamic code generation pattern.
assets/page-builder/js/grapesjs-plugin-export.jsView on unpkg · L1fesm2022/inchurch-matcha-components.mjsView file
Findings
2 Critical1 High4 Medium5 Low
CriticalTrojan Source Unicodefesm2022/inchurch-matcha-components.mjs
CriticalTrigger Reachable Dangerous Capabilityfesm2022/inchurch-matcha-components.mjs
HighAi Review Evidencefesm2022/inchurch-matcha-components.mjs
MediumDynamic Requireassets/page-builder/js/grapesjs-plugin-export.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowEvalassets/page-builder/js/grapesjs-plugin-export.js
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @inchurch/matcha-components@22.42.1.
See all versions of @inchurch/matcha-components for other recorded verdicts.
- Avoid installing @inchurch/matcha-components@22.42.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.