registry / Data exfiltration / @playerdata-internal/playerdata-core
@playerdata-internal/playerdata-core
This report shows the evidence for @playerdata-internal/playerdata-core@9999.99.20, the only known version.
This package appears in our research on the dependency confusion probes at version 99 and above, with how it works, the full package list and what to do if you installed it.
AI Security Review
scanned 4mo ago · by lpm-firewall-aiSource inspection confirms unconsented install-time collection and exfiltration of host identity data to an unrelated webhook endpoint. This is concrete malicious behavior, not merely dual-use networking.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
npm install lifecycle postinstall
Impact
Leaks installer username, working directory, hostname, local IP, platform, and timestamp to an external webhook.
Mechanism
install-time host fingerprint exfiltration via HTTPS POST
Attack narrative
On installation, npm runs the postinstall script `node index.js`. That script builds a JSON payload from OS and process metadata, including username, project working directory, hostname, local IPv4 address, platform, and timestamp, then posts it to a webhook.site URL. There is no visible legitimate package behavior that requires this install-time telemetry.
AI rationale
Source inspection confirms unconsented install-time collection and exfiltration of host identity data to an unrelated webhook endpoint. This is concrete malicious behavior, not merely dual-use networking.
Evidence
package.jsonindex.js
Network endpoints1
webhook.site/a8cd7fd0-4d41-4806-8649-f3297e94a008
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- package.json defines postinstall: node index.js
- index.js runs at install time and immediately sends an HTTPS POST
- index.js collects os.userInfo().username, cwd/INIT_CWD, hostname, local IPv4, platform, timestamp
- Data is exfiltrated to webhook.site /a8cd7fd0-4d41-4806-8649-f3297e94a008
- No package functionality beyond install-time host fingerprint collection and network send
Evidence against
- No credential file reads observed
- No child_process, eval, persistence, destructive actions, or AI-agent config writes observed
Behavioral surface
EnvironmentVarsNetwork
Source & flagged code
3 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node index.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkgindex.jsView file
1const os = require('os');
L2: const https = require('https');
L3:
L4: function localIP() {
L5: const nets = os.networkInterfaces();
L6: for (const iface of Object.values(nets)) {
...
L15: user: os.userInfo().username,
L16: cwd: process.env.INIT_CWD || process.cwd(),
L17: hostname: os.hostname(),
L18: localIP: localIP(),
...
L40:
L41: req.write(payload);
High
Host Fingerprint Exfiltration
Source collects local host identity data and sends it to an external endpoint.
index.jsView on unpkg · L1•matchType = malicious_source_fingerprint_signature
signature = b6b657094c077e81
signatureType = suspicious_hashes
sourceLabel = final_verdict:malicious
matchedPackage = dependency_confusions@99.9.9
matchedPath = index.js
matchedIdentity = npm:ZGVwZW5kZW5jeV9jb25mdXNpb25z:99.9.9
similarity = 1.000
shingleOverlap = 1
summary = package final verdict is malicious
Findings
3 High2 Medium1 Low
HighInstall Time Lifecycle Scriptspackage.json
HighHost Fingerprint Exfiltrationindex.js
HighKnown Malware Source Fingerprint Signatureindex.js
MediumNetwork
MediumEnvironment Vars
LowScripts Present
Affected versions and remediation
This report applies to @playerdata-internal/playerdata-core@9999.99.20.
The versions list below shows the verdict for each recorded version.
- Avoid installing @playerdata-internal/playerdata-core@9999.99.20. 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.