@aj-shadow/actorjs-app@0.0.0-aj-beta.264
Library used by @aj-shadow/actorjs
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe manifest activates the installer automatically, and inspected source confirms recursive deletion and replacement of consumer project paths without a consent guard. This is malicious install-hook behavior that can destroy or overwrite consumer files.
Static reason
High-risk behavior combination matched malicious policy.; source fingerprint signature matched known malicious package; routed for review
Trigger
Installing the package with npm, which invokes its postinstall hook.
Impact
Existing consumer project content can be destroyed or replaced during installation.
Mechanism
The installer computes paths above its own directory, recursively removes destination paths, and renames package content into those locations.
Attack narrative
The package's automatic postinstall loads an installer that reaches above the package directory into the consumer project. It recursively deletes target paths before moving package files into them, and separately removes build, dist, and temp directories. This creates a concrete install-time destructive file mutation surface.
AI rationale
The manifest activates the installer automatically, and inspected source confirms recursive deletion and replacement of consumer project paths without a consent guard. This is malicious install-hook behavior that can destroy or overwrite consumer files.
Evidence
package.jsonnpm-post-install.js.vscodeprojectworkspaceREADME.mdCHANGELOG.mdcontributors.txtsettings.jsonmain.jsrepos.jsonbuilddisttemp
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- package.json runs npm-post-install.js automatically through a postinstall hook.
- The installer targets paths six directories above its package location, reaching the consumer project root in a standard nested npm installation.
- The postinstall recursively deletes existing destination paths, then moves package files over them; targets include .vscode, project, workspace, settings.json, main.js, and repos.json.
- The same install hook recursively removes build, dist, and temp directories three levels above the package.
Evidence against
Behavioral surface
ChildProcessDynamicRequireEnvironmentVarsEvalFilesystemShellWebSocket
HighEntropyStringsUrlStrings
Source & flagged code
5 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node -e "try{require('./npm[redacted]')}catch(e){console.log(e);}"
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('./npm[redacted]')}catch(e){console.log(e);}"
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkgproject/server/plugin-data/repos/plugin_data_ReposVerifyGit.jsView file
3L4: const PluginBaseMulti = require('z-abs-corelayer-server/server/plugin-base-multi');
L5: const Os = require('os');
Medium
Dynamic Require
Findings
1 Critical3 High3 Medium5 Low
CriticalRed Install Lifecycle Scriptpackage.json
HighInstall Time Lifecycle Scriptspackage.json
HighSemantic Analysis Limitedproject/server/plugin-data/test-suite/plugin_data_TestSuiteExecutionStart.js
HighKnown Malware Source Fingerprint Signaturenpm-post-install.js
MediumDynamic Requireproject/server/plugin-data/repos/plugin_data_ReposVerifyGit.js
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowEval
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @aj-shadow/actorjs-app@0.0.0-aj-beta.264.
See all versions of @aj-shadow/actorjs-app for other recorded verdicts.
- Avoid installing @aj-shadow/actorjs-app@0.0.0-aj-beta.264. 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.