Which versions of 8-fetchsight-web are malicious?

The following npm versions of 8-fetchsight-web are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate 8-fetchsight-web if I installed it?

Remove 8-fetchsight-web 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 8-fetchsight-web — how do I know if it already compromised me?

If 8-fetchsight-web 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 8-fetchsight-web part of a known attack campaign?

Yes — 8-fetchsight-web is associated with the IN-MAL-2026-018576, IN-MAL-2026-018578 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 8-fetchsight-web across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for 8-fetchsight-web (2 malicious versions).

Malicious package

8-fetchsight-webnpm

Advisory published Aug 23, 2026Updated Aug 23, 2026

8-fetchsight-web is a confirmed malicious npm package (MAL-2026-14366) that executes malicious code on install (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in 8-fetchsight-web (npm)

MAL-2026-14366

Immediate action

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

npm uninstall 8-fetchsight-web

What this malware does

index.js and index.html contain a top-level IIFE that fetches https://bitbucket.org/p2p-alt-public/p2p-emis/raw/main/GameWebSight, parses the response as HTML, replaces the current document, and re-creates every <script> tag so both inline and remote-src scripts from the fetched document execute in the page context. The URL is pinned to the mutable main branch of a Bitbucket workspace unrelated to the npm publisher, so whoever controls that Bitbucket path can substitute arbitrary JavaScript at any time and have it executed in every page that loads this package. The advertised 'website loader for remote HTML content' purpose is served by an arbitrary-code-execution mechanism with no integrity check, no pinning, and no publisher-controlled source.

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

d0e6a4c6ee9a60609bc1a9e9f1eccfa2166aaf106ba50c35d51aac34ecb3f549

f8c9c836d052e62ba469fedd5a0e0d64563f15ee95b70f2b295bcfe5f7a68371

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for 8-fetchsight-web (2 malicious versions).
If you installed it — respond
Remove 8-fetchsight-web 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 8-fetchsight-web 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. 8-fetchsight-web on npm has been identified as a malicious package (versions 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018576IN-MAL-2026-018578

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks 8-fetchsight-web-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