@aj-shadow/actorjs-app@0.0.0-aj-beta.270
Library used by @aj-shadow/actorjs
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe postinstall hook automatically performs destructive changes to the parent application and edits user shell startup files. This is concrete install-time abuse, so the package should be blocked.
Static reason
High-risk behavior combination matched malicious policy.; source fingerprint signature matched known malicious package; routed for review
Trigger
Installing the package through npm, which invokes its postinstall hook.
Impact
Installation can remove application build data, relocate application files, and leave persistent shell aliases in the user’s startup configuration.
Mechanism
The hook runs npm-post-install.js, which executes a temporary shell script, edits shell startup files, recursively deletes directories, and moves files to parent directories.
Attack narrative
Installing the package automatically invokes an installer that reaches above its own directory. It recursively removes the parent application’s build, dist, and temp directories, moves project files into that directory, and runs a shell script that can append aliases to user startup files. These unrequested destructive and persistent changes support blocking publication.
AI rationale
The postinstall hook automatically performs destructive changes to the parent application and edits user shell startup files. This is concrete install-time abuse, so the package should be blocked.
Evidence
package.jsonnpm-post-install.js.bashrc.zshrcbuild/dist/temp/.vscodeprojectworkspaceREADME.mdCHANGELOG.mdmain.jsrepos.json
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- package.json runs npm-post-install.js automatically from its postinstall hook.
- The installer derives paths above the package and then runs file creation, cleanup, and file moves without a consent check.
- On Linux and macOS, the installer runs a temporary shell script that appends aliases to the user’s shell startup files.
- The postinstall cleanup recursively deletes the parent application’s build, dist, and temp directories.
- The installer moves package files and directories, including .vscode, project, and workspace, to the parent application directory.
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.270.
See all versions of @aj-shadow/actorjs-app for other recorded verdicts.
- Avoid installing @aj-shadow/actorjs-app@0.0.0-aj-beta.270. 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.