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?

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

If ipy-rev-proxy 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 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?

Search your lockfiles and build artifacts for ipy-rev-proxy (version 9.3.1).

Malicious package

ipy-rev-proxynpm

Advisory published Jun 9, 2026Updated Jun 9, 2026

ipy-rev-proxy is a confirmed malicious npm package (MAL-2026-5475) that executes malicious code on install (malicious version 9.3.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ipy-rev-proxy (npm)

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

Malicious package

Find it
Search your lockfiles and build artifacts for ipy-rev-proxy (version 9.3.1).
If you installed it — respond
Remove ipy-rev-proxy 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 ipy-rev-proxy 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. 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 malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database