Which versions of int-browsing-gateway are malicious?

The following npm versions of int-browsing-gateway are flagged malicious: 1.0.4. Treat any of these as compromised.

How do I remediate int-browsing-gateway if I installed it?

Remove int-browsing-gateway 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 int-browsing-gateway — how do I know if it already compromised me?

If int-browsing-gateway 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 int-browsing-gateway part of a known attack campaign?

Yes — int-browsing-gateway is associated with the RLMA-2026-01977 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 int-browsing-gateway across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for int-browsing-gateway (version 1.0.4).

Malicious package

int-browsing-gatewaynpm

Advisory published Apr 16, 2026Updated Apr 23, 2026

int-browsing-gateway is a confirmed malicious npm package (MAL-2026-2776) that executes malicious code on install (malicious version 1.0.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in int-browsing-gateway (npm)

MAL-2026-2776

Immediate action

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

npm uninstall int-browsing-gateway

What this malware does

The package int-browsing-gateway was found to contain malicious code.

Malicious versions

1 flagged

1.0.4

Indicators of compromise (SHA-256)

5581cf53cf3f8a01e58b31b32a3fe3bb237864e2ef1c53d2ad4d8cfab77f6c1a

91651e0df0a67cf6185a611e7636862de6fb619d7eecf1952902fccc6171b687

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for int-browsing-gateway (version 1.0.4).
If you installed it — respond
Remove int-browsing-gateway 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 int-browsing-gateway 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. int-browsing-gateway on npm has been identified as a malicious package (version 1.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01977

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks int-browsing-gateway-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