registry / Data exfiltration / @iflyrpa/actions
@iflyrpa/actions
@iflyrpa/playwright 包中发布逻辑的具体实现
This report shows the evidence for @iflyrpa/actions@4.1.0. 1 of 7 known versions is blocked or flagged. The newest version, 4.1.3, is flagged. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe automatic external transmission of full request URLs and errors is a concrete data-exfiltration behavior. The absence of install hooks limits scope but does not neutralize this runtime disclosure.
Static reason
One or more suspicious static signals were detected.
Trigger
A consumer invokes an action whose HTTP request fails.
Impact
Request URLs and error text, including possible query credentials or private identifiers, can be disclosed to the webhook operator.
Mechanism
Hard-coded webhook telemetry posts request failure details.
Attack narrative
A failed action builds a report containing the HTTP method, complete URL, error message, and status. It then posts that report to a fixed webhook controlled outside the consumer's configured endpoints. Because action URLs may contain user data or credentials and the telemetry is automatic and not configurable, this is concrete runtime data exfiltration. The same module also loads an opaque signer when Xiaohongshu signing is used.
AI rationale
The automatic external transmission of full request URLs and errors is a concrete data-exfiltration behavior. The absence of install hooks limits scope but does not neutralize this runtime disclosure.
Evidence
dist/index.mjs
Network endpoints1
open.xfchat.iflytek.com
Decision evidence
public snapshotAI called this Malicious at 90.0% confidence as Malware with low false-positive risk.
Evidence for block
- A hard-coded external webhook receives runtime failure reports through axios.
- Failure reports include the full request URL and an error message, which can expose user-supplied query data.
- A Xiaohongshu signing path imports an opaque, encoded implementation at runtime.
Evidence against
- package.json has no install or postinstall lifecycle hook.
- No child-process execution, environment harvesting, or broad filesystem collection was found.
- Most network calls implement the package's social-media automation actions.
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsPossibleObfuscationUrlStrings
Source & flagged code
5 flagged · loading sourcedist/bundle.jsView file
9716if (_0x383dd4 === _0x16c0e0) break;
L9717: _0x46fb59['push'](_0x46fb59['shift']());
L9718: } catch (_0x4fc071) {
High
Obfuscated Payload Loader
Source contains an obfuscated payload loader that reconstructs and executes hidden code.
dist/bundle.jsView on unpkg · L971611818};
L11819: const _0x2055b1 = new function() {
L11820: eval('this[\'a\'] = 2;');
Low
Eval
Package source references a known benign dynamic code generation pattern.
dist/bundle.jsView on unpkg · L1181855const buf = await toBuffer(stream);
L56: const str = buf.toString('utf8');
L57: try {
...
L69: const promise = new Promise((resolve, reject)=>{
L70: req1.once('response', resolve).once('error', reject).end();
L71: });
...
L624: } catch (error) {}
L625: if (!r && 'undefined' != typeof process && 'env' in process) r = process.env.DEBUG;
L626: return r;
...
L797: const supportsColor = __webpack_require__("../../node_modules/.pnpm/supports-color@8.1.1/node_modules/supports-color/index.js");
L798: if (supportsColor && (supportsColor.stderr || supportsColor).level >= 2) exports1.colors = [
L799: 20,
Low
Weak Crypto
Package source references weak cryptographic algorithms.
dist/bundle.jsFindings
3 High3 Medium6 Low
HighObfuscated Payload Loaderdist/bundle.js
HighAi Review Evidencedist/index.mjs
HighAi Review Evidencedist/index.mjs
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowEvaldist/bundle.js
LowWeak Cryptodist/bundle.js
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @iflyrpa/actions@4.1.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing @iflyrpa/actions@4.1.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.