Malicious code in poly-custom-api (npm)
The poly-custom-api npm package version 5.3.1 contains malicious code that fetches and executes remote code from an untrusted IP address. The package's default export constructs an HTTPS URL to a bare IP and evaluates the fetched response as code with full host privileges. This behavior allows arbitrary code execution in the Node.js process of any user invoking the function. The malicious payload is mutable, unauthenticated, and disguised using icon-related naming to evade detection.
AI Analysis
Technical Summary
In poly-custom-api version 5.3.1, the default exported function getPlugin constructs an HTTPS URL targeting the IP 46.183.25.232 on port 45000, fetching data from /icons/108. The response's data.credits field is passed to a new Function(...) call with Node.js globals injected, enabling remote arbitrary code execution with full host privileges. The endpoint is disguised with icon and CDN-related vocabulary, while the package advertises itself as a custom API library. The payload is mutable, unpinned, and served from infrastructure unrelated to any legitimate publisher, indicating malicious intent.
Potential Impact
Any user or system that installs and invokes the poly-custom-api package version 5.3.1 risks executing arbitrary code controlled by an attacker. This can lead to full compromise of the Node.js process and potentially the host system, as the remote code runs with full privileges. The unauthenticated and mutable nature of the payload increases the risk of ongoing malicious activity and dynamic payload changes.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should immediately cease using poly-custom-api version 5.3.1 and remove it from their environments. Avoid invoking the getPlugin function or any code from this package. Monitor for updates from the package maintainer or trusted sources for any official fixes or advisories. Consider replacing this package with a trusted alternative.
Malicious code in poly-custom-api (npm)
Description
The poly-custom-api npm package version 5.3.1 contains malicious code that fetches and executes remote code from an untrusted IP address. The package's default export constructs an HTTPS URL to a bare IP and evaluates the fetched response as code with full host privileges. This behavior allows arbitrary code execution in the Node.js process of any user invoking the function. The malicious payload is mutable, unauthenticated, and disguised using icon-related naming to evade detection.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
In poly-custom-api version 5.3.1, the default exported function getPlugin constructs an HTTPS URL targeting the IP 46.183.25.232 on port 45000, fetching data from /icons/108. The response's data.credits field is passed to a new Function(...) call with Node.js globals injected, enabling remote arbitrary code execution with full host privileges. The endpoint is disguised with icon and CDN-related vocabulary, while the package advertises itself as a custom API library. The payload is mutable, unpinned, and served from infrastructure unrelated to any legitimate publisher, indicating malicious intent.
Potential Impact
Any user or system that installs and invokes the poly-custom-api package version 5.3.1 risks executing arbitrary code controlled by an attacker. This can lead to full compromise of the Node.js process and potentially the host system, as the remote code runs with full privileges. The unauthenticated and mutable nature of the payload increases the risk of ongoing malicious activity and dynamic payload changes.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should immediately cease using poly-custom-api version 5.3.1 and remove it from their environments. Avoid invoking the getPlugin function or any code from this package. Monitor for updates from the package maintainer or trusted sources for any official fixes or advisories. Consider replacing this package with a trusted alternative.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-12416
- Osv Schema Version
- 1.7.4
- Ecosystems
- ["npm"]
Threat ID: 6a735743bf8831d539159c5c
Added to database: 08/05/2026, 15:31:15 UTC
Last enriched: 08/05/2026, 17:17:32 UTC
Last updated: 09/07/2026, 22:29:15 UTC
Views: 51
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.