Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

redeem-onchain-sdknpm

Malicious code in redeem-onchain-sdk (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3182
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall redeem-onchain-sdk

What this malware does

redeem-onchain-sdk is a malicious npm package impersonating a Polymarket on-chain SDK. It collects SSH keys, AWS credentials, .npmrc tokens, Docker auth, Chrome saved logins, .env files, and a month of git commit history, then ships everything over a raw TCP socket to an AWS-hosted C2. Two triggers fire it: a require() side effect in the package's main entry point (added in v1.0.1) and a postinstall hook (added in v1.0.5). The payload lives in dist/proxy.js, later renamed dist/index5_test.js.

The package redeem-onchain-sdk was found to contain malicious code.

Malicious versions

1 flagged
1.0.7

Indicators of compromise (SHA-256)

765d01eed7c5ad80c911fec6f2e1778fb2c14fa7165520416d85273858f7e3e3

Detection & response playbook

Credential / info stealer
  1. Find it

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

  2. If you installed it — respond

    redeem-onchain-sdk 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.

  3. Did it already run?

    If redeem-onchain-sdk 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.

  4. How O3 protects you

    O3 blocks redeem-onchain-sdk 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. redeem-onchain-sdk on npm has been identified as a malicious package (version 1.0.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

  • Amazon Inspector · finder
  • SafeDep · finder

Detect & block this

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

redeem-onchain-sdk (npm) malicious package — MAL-2026-3182 | O3 Security