Which versions of ipy-rev-proxy are malicious?

The following npm versions of ipy-rev-proxy are flagged malicious: 9.3.1. Treat any of these as compromised.

How do I remediate ipy-rev-proxy if I installed it?

ipy-rev-proxy 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 ipy-rev-proxy — how do I know if it already compromised me?

If ipy-rev-proxy 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 ipy-rev-proxy part of a known attack campaign?

Yes — ipy-rev-proxy is associated with the IN-MAL-2026-005194, IN-MAL-2026-005195 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 ipy-rev-proxy 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 ipy-rev-proxy (version 9.3.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ipy-rev-proxy across your stack and pipelines.

Malicious package

ipy-rev-proxynpm

Malicious code in ipy-rev-proxy (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5475

Immediate action

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

npm uninstall ipy-rev-proxy

What this malware does

On npm install, index.js runs as a preinstall hook and POSTs hostname, username, platform, architecture, cwd, CI flags, and npm user-agent to https://webhook.site/40b5f3e2-4072-4f2c-b259-0ecb531755d7. The same script then probes Google's internal SSO proxy at http://uberproxy.corp.google.com/procz and the GCE metadata endpoint http://metadata.google.internal/computeMetadata/v1/instance/service-accounts/default/token (with the required Metadata-Flavor: Google header) and forwards any 200 response — including GCE service-account tokens — plus hostname, id, and uname -a output to the same webhook. The package presents itself with a generic Jupyter description and the placeholder author 'IPython Development Team' but ships no functional code matching that description; the name and metadata are consistent with a dependency-confusion lure aimed at Google internal builds.

Malicious versions

1 flagged

9.3.1

Indicators of compromise (SHA-256)

591a0d253aee02115544f9bcac7609e62d8c18a9ac60cc4967d7d6e8c7f7d555

5b5e8b8bd7fa1b9720229e7ba23e00e08a5a843e209fc8525d58a05ea3e70321

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 ipy-rev-proxy (version 9.3.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ipy-rev-proxy across your stack and pipelines.
If you installed it — respond
ipy-rev-proxy 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 ipy-rev-proxy 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 ipy-rev-proxy 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. ipy-rev-proxy on npm has been identified as a malicious package (version 9.3.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-005194IN-MAL-2026-005195

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ipy-rev-proxy-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