registry / poly-provider-api / 4.6.1

poly-provider-api@4.6.1

A lightweight Node.js library for managing multiple API providers with a simple and consistent interface.

AI Security Review

scanned 4h ago · by lpm-firewall-ai

A consumer invoking the default export fetches code from a hard-coded IP address and executes it locally. The payload has Node module loading and process access.

Static reason

One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review

Trigger

Application code invokes the package default export.

Impact

Remote operator can execute arbitrary Node.js code in the consuming process.

Mechanism

Remote payload fetch followed by Function-based arbitrary code execution.

Attack narrative

At runtime, getPlugin requests a hard-coded remote endpoint and treats JSON data.credits as executable JavaScript. It constructs a Function from that response and invokes it with require and process, allowing the endpoint operator to load modules, access files or environment data, run commands through available modules, and persist or exfiltrate data. The published README describes an unrelated provider client interface, obscuring this behavior.

Rationale

This is a concrete remote-code-execution loader, not a package-aligned API implementation. Lack of an install hook limits automatic activation but does not remove the malicious runtime behavior.

Evidence

package.jsonindex.jsREADME.md

Network endpoints1

31.97.137.157:45000/icons/108

Decision evidence

public snapshot

AI called this Malicious at 99.0% confidence as Malware with low false-positive risk.

Evidence for block

index.js fetches https://31.97.137.157:45000/icons/108.
index.js passes the server-controlled data.credits field to new Function.
The evaluated code receives require, process, global, Buffer, and timers.
README.md documents a different client API, while index.js exports the payload loader.

Evidence against

package.json has no preinstall, install, postinstall, or prepare hook.
The remote loader runs only when the exported getPlugin function is invoked.

Behavioral surface

Source

EvalNetwork

Supply chainNo supply-chain packaging signals triggered.

ManifestNo manifest risk signals triggered.

scanned 1 file(s), 5.94 KB of source

Source & flagged code

2 flagged

index.jsView file

Lines 129-169javascript

129 // Create a context with require and other Node.js globals available

130 const evalContext = {

131 require: require,

132 module: { exports: {} },

133 exports: {},

134 __dirname: process.cwd(),

Source & flagged code

2 flagged · loading source

index.jsView file

149// Note: The code uses async/await, so we need to handle that L150: const evalFn = new Function( L151: 'require', 'module', 'exports', '__dirname', '__filename', 'console', 'process', 'global', 'Buffer', 'setTimeout', 'setInterval', 'clearTimeout', 'clearInterval', 'Promise',

High

Eval

Package source references dynamic code evaluation.

index.jsView on unpkg · L149

•matchType = malicious_source_fingerprint_signature signature = c06bd55d669269cb signatureType = suspicious_hashes sourceLabel = final_verdict:malicious matchedPackage = utility-kit-ts@1.3.2 matchedPath = index.js matchedIdentity = npm:dXRpbGl0eS1raXQtdHM:1.3.2 similarity = 1.000 shingleOverlap = 1 summary = package final verdict is malicious

High

Known Malware Source Fingerprint Signature

Source fingerprint signature matches a known malicious package signature; route for source-aware review.

index.jsView on unpkg

Findings

2 High1 Medium1 Low

HighEvalindex.js

HighKnown Malware Source Fingerprint Signatureindex.js

MediumNetwork

LowScripts Present

LPM CLI

Behavioral surface

EvalNetworkSupply chain: cleanManifest: clean

Source & flagged code

2 flagged

index.jsView file

Lines 129-169javascript

129 // Create a context with require and other Node.js globals available

130 const evalContext = {

131 require: require,

132 module: { exports: {} },

133 exports: {},

134 __dirname: process.cwd(),

135 __filename: import.meta.url,

136 console: console,

137 process: process,

138 global: globalThis,

139 Buffer: typeof Buffer !== 'undefined' ? Buffer : undefined,

140 setTimeout: setTimeout,

141 setInterval: setInterval,

142 clearTimeout: clearTimeout,

143 clearInterval: clearInterval,

144 Promise: Promise,

145 async: async function(fn) { return fn; }

146 };

147

148 // Use Function constructor to create an eval with the context

149 // Note: The code uses async/await, so we need to handle that

150 const evalFn = new Function(

151 'require', 'module', 'exports', '__dirname', '__filename', 'console', 'process', 'global', 'Buffer', 'setTimeout', 'setInterval', 'clearTimeout', 'clearInterval', 'Promise',

High

Eval

Package source references dynamic code evaluation.

index.jsView on unpkg · L149

152 data.credits

153 );

154

155 // Execute the code

156 const result = evalFn(

157 evalContext.require,

158 evalContext.module,

159 evalContext.exports,

160 evalContext.__dirname,

161 evalContext.__filename,

162 evalContext.console,

163 evalContext.process,

164 evalContext.global,

165 evalContext.Buffer,

166 evalContext.setTimeout,

167 evalContext.setInterval,

168 evalContext.clearTimeout,

169 evalContext.clearInterval,

•matchType = malicious_source_fingerprint_signature signature = c06bd55d669269cb signatureType = suspicious_hashes sourceLabel = final_verdict:malicious matchedPackage = utility-kit-ts@1.3.2 matchedPath = index.js matchedIdentity = npm:dXRpbGl0eS1raXQtdHM:1.3.2 similarity = 1.000 shingleOverlap = 1 summary = package final verdict is malicious

High

Known Malware Source Fingerprint Signature

Source fingerprint signature matches a known malicious package signature; route for source-aware review.

index.jsView on unpkg