Which versions of poly-bbc-service are malicious?

The following npm versions of poly-bbc-service are flagged malicious: 3.7.2. Treat any of these as compromised.

How do I remediate poly-bbc-service if I installed it?

poly-bbc-service is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed poly-bbc-service — how do I know if it already compromised me?

If poly-bbc-service was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is poly-bbc-service part of a known attack campaign?

Yes — poly-bbc-service is associated with the IN-MAL-2026-014926 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-bbc-service across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for poly-bbc-service (version 3.7.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging poly-bbc-service across your stack and pipelines.

Malicious package

poly-bbc-servicenpm

poly-bbc-service is a confirmed malicious npm package (MAL-2026-12799) that steals credentials and exfiltrates sensitive data (malicious version 3.7.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in poly-bbc-service (npm)

MAL-2026-12799

Immediate action

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

npm uninstall poly-bbc-service

What this malware does

The package's exported getPlugin function issues an HTTPS request to the hardcoded bare-IP endpoint https://46.183.25.232:45000/icons/107 and passes the response's data.credits field into new Function('require','module','exports',...,'Promise', data.credits) for execution. The generated function receives require, module, exports, process, and Buffer, giving the fetched payload full Node.js privileges on the consumer's machine. An unused setDefaultModule helper constructs plausible cdnjs.cloudflare.com/font-awesome URLs that are never used at runtime, providing a cover story inconsistent with both the README (advertised as a Polymarket client) and the actual runtime target. Declared runtime dependencies include @primno/dpapi (Windows DPAPI bindings), better-sqlite3, and node-machine-id, which are consistent with staging for browser-credential / DPAPI-protected secret extraction once the remote payload is delivered.

Malicious versions

1 flagged

3.7.2

Indicators of compromise (SHA-256)

3bb49d43833628610acae14ea039bb3a490dc94ec90bd8faac084a977a8f8ebd

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for poly-bbc-service (version 3.7.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging poly-bbc-service across your stack and pipelines.
If you installed it — respond
poly-bbc-service is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If poly-bbc-service was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks poly-bbc-service before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

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

Campaign

IN-MAL-2026-014926

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks poly-bbc-service-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database