Which versions of poly-custom-api are malicious?

The following npm versions of poly-custom-api are flagged malicious: 5.3.1. Treat any of these as compromised.

How do I remediate poly-custom-api if I installed it?

Remove poly-custom-api from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed poly-custom-api — how do I know if it already compromised me?

If poly-custom-api was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is poly-custom-api part of a known attack campaign?

Yes — poly-custom-api is associated with the IN-MAL-2026-014848, RLMA-2026-10777 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find poly-custom-api across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for poly-custom-api (version 5.3.1).

Malicious package

poly-custom-apinpm

Advisory published Aug 5, 2026Updated Sep 24, 2026

poly-custom-api is a confirmed malicious npm package (MAL-2026-12416) that executes malicious code on install (malicious version 5.3.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in poly-custom-api (npm)

MAL-2026-12416

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall poly-custom-api

What this malware does

The default export getPlugin in index.js constructs an HTTPS URL from split constants pointing at the bare IP 46.183.25.232:45000/icons/108, fetches the response, and passes the response field data.credits to new Function(...) with require, module, exports, process, Buffer, and global injected as parameters. Any caller invoking the exported function grants the remote endpoint arbitrary code execution in the Node.js process with full host privileges. The endpoint is disguised with icon/CDN vocabulary (iconDomain, font-awesome/svgs/brands, a 'bearrtoken' field literal 'logo') and an unused IconProvider map, while the package advertises itself as a 'custom API library' — the icon framing is cover for the fetch-and-eval path. The payload is mutable, unpinned, unauthenticated, and served over a bare-IP host unrelated to any legitimate publisher infrastructure.

Malicious versions

1 flagged

5.3.1

Indicators of compromise (SHA-256)

a3263a9e2a986068fafa530a8e6862f9ba41cad05ecbd5b7b91752ca1c5af0c6

844e3e52bd0aba032142b3cc4455f99416b4375d4ba9d5a0862fc96b926884fc

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for poly-custom-api (version 5.3.1).
If you installed it — respond
Remove poly-custom-api from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If poly-custom-api was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. poly-custom-api on npm has been identified as a malicious package (version 5.3.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014848RLMA-2026-10777

References

npmjs.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks poly-custom-api-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database