registry / Remote code execution / poly-custom-api
poly-custom-api
A lightweight Node.js library for building and integrating custom APIs with database, networking, and utility support.
This report shows the evidence for poly-custom-api@5.3.1, the only known version.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe source contains a concrete, user-triggered remote code execution chain with no integrity or trust validation. Lack of install hooks limits automatic activation but does not make the exported behavior benign.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
Runtime invocation of the default-exported getPlugin function.
Impact
Arbitrary code execution in the consuming process, enabling subsequent data theft, persistence, or destructive actions.
Mechanism
Remote payload download followed by Function-constructor execution.
Attack narrative
A consumer that calls the default export causes a request to the hard-coded IP endpoint. The response’s credits field is supplied directly to new Function and invoked with require, process, global, and Buffer available, so the endpoint can run arbitrary Node.js code in the consumer’s context.
AI rationale
The source contains a concrete, user-triggered remote code execution chain with no integrity or trust validation. Lack of install hooks limits automatic activation but does not make the exported behavior benign.
Evidence
index.jspackage.json
Network endpoints1
46.183.25.232:45000/icons/108
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- index.js exports getPlugin, which fetches https://46.183.25.232:45000/icons/108 by default.
- index.js passes server-controlled data.credits to new Function and executes it.
- The evaluated payload receives require, process, global, Buffer, and timer APIs.
- Remote payload execution is triggered by calling the package’s default export.
Evidence against
- package.json has no preinstall, install, or postinstall lifecycle hook.
- Inspected source contains no package-side file writes or credential collection before payload execution.
Behavioral surface
EvalNetwork
Source & flagged code
2 flagged · loading sourceindex.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
•matchType = malicious_source_fingerprint_signature
signature = c06bd55d669269cb
signatureType = suspicious_hashes
sourceLabel = final_verdict:malicious
matchedPackage = poly-bbc-service@3.7.2
matchedPath = index.js
matchedIdentity = npm:cG9seS1iYmMtc2VydmljZQ:3.7.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 unpkgFindings
2 High1 Medium1 Low
HighEvalindex.js
HighKnown Malware Source Fingerprint Signatureindex.js
MediumNetwork
LowScripts Present
Affected versions and remediation
This report applies to poly-custom-api@5.3.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing poly-custom-api@5.3.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.