webshell

Ghost Exploiter Team Official

Directory >> /home/softsuitetech/.npm/_logs/

File / Folder	Size	Action
.	-
2021-12-27T06_08_58_409...	2.683KB	edt ren
2021-12-27T06_08_58_428...	2.011KB	edt ren
2022-01-18T11_57_07_082...	2.722KB	edt ren
2022-01-18T11_57_07_103...	2.067KB	edt ren
2023-01-05T10_56_32_400...	3.191KB	edt ren
2023-01-05T10_57_31_156...	3.334KB	edt ren
2023-01-05T11_59_31_923...	3.182KB	edt ren
2023-01-05T12_04_05_489...	3.182KB	edt ren
2023-01-05T13_12_09_098...	3.182KB	edt ren
2023-01-06T11_01_33_230...	3.182KB	edt ren

0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli   '/opt/alt/alt-nodejs14/root/usr/bin/node',
1 verbose cli   '/opt/alt/alt-nodejs14/root/usr/bin/npm',
1 verbose cli   'run-script',
1 verbose cli   'crow',
1 verbose cli   '--'
1 verbose cli ]
2 info using npm@6.14.17
3 info using node@v14.20.1
4 verbose run-script [ 'precrow', 'crow', 'postcrow' ]
5 info lifecycle server@1.0.0~precrow: server@1.0.0
6 info lifecycle server@1.0.0~crow: server@1.0.0
7 warn lifecycle The node binary used for scripts is /home/softsuitetech/nodevenv/public_html/DEMO/gotem-platform-backend/14/bin/node but npm is using /opt/alt/alt-nodejs14/root/usr/bin/node itself. Use the `--scripts-prepend-node-path` option to include the path for the node binary npm was executed with.
8 verbose lifecycle server@1.0.0~crow: unsafe-perm in lifecycle true
9 verbose lifecycle server@1.0.0~crow: PATH: /opt/alt/alt-nodejs14/root/usr/lib/node_modules/npm/node_modules.bundled/npm-lifecycle/node-gyp-bin:/home/softsuitetech/public_html/DEMO/gotem-platform-backend/node_modules/.bin:/home/softsuitetech/nodevenv/public_html/DEMO/gotem-platform-backend/14/bin:/opt/alt/alt-nodejs14/root/usr/bin:/home/softsuitetech/nodevenv/public_html/DEMO/gotem-platform-backend/14/lib/bin/:/usr/local/jdk/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/usr/local/bin:/usr/X11R6/bin:/root/bin:/opt/bin
10 verbose lifecycle server@1.0.0~crow: CWD: /home/softsuitetech/public_html/DEMO/gotem-platform-backend
11 silly lifecycle server@1.0.0~crow: Args: [
11 silly lifecycle   '-c',
11 silly lifecycle   'NODE_ENV=production env-cmd -f ./.env.production node index.js'
11 silly lifecycle ]
12 silly lifecycle server@1.0.0~crow: Returned: code: 1  signal: null
13 info lifecycle server@1.0.0~crow: Failed to exec crow script
14 verbose stack Error: server@1.0.0 crow: `NODE_ENV=production env-cmd -f ./.env.production node index.js`
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter.<anonymous> (/opt/alt/alt-nodejs14/root/usr/lib/node_modules/npm/node_modules.bundled/npm-lifecycle/index.js:332:16)
14 verbose stack     at EventEmitter.emit (events.js:400:28)
14 verbose stack     at ChildProcess.<anonymous> (/opt/alt/alt-nodejs14/root/usr/lib/node_modules/npm/node_modules.bundled/npm-lifecycle/lib/spawn.js:55:14)
14 verbose stack     at ChildProcess.emit (events.js:400:28)
14 verbose stack     at maybeClose (internal/child_process.js:1088:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:296:5)
15 verbose pkgid server@1.0.0
16 verbose cwd /home/softsuitetech/public_html/DEMO/gotem-platform-backend
17 verbose Linux 4.18.0-372.19.1.lve.el7h.x86_64
18 verbose argv "/opt/alt/alt-nodejs14/root/usr/bin/node" "/opt/alt/alt-nodejs14/root/usr/bin/npm" "run-script" "crow" "--"
19 verbose node v14.20.1
20 verbose npm  v6.14.17
21 error code ELIFECYCLE
22 error errno 1
23 error server@1.0.0 crow: `NODE_ENV=production env-cmd -f ./.env.production node index.js`
23 error Exit status 1
24 error Failed at the server@1.0.0 crow script.
24 error This is probably not a problem with npm. There is likely additional logging output above.
25 verbose exit [ 1, true ]

<=Back