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

10-shardsight-webnpm

10-shardsight-web is a confirmed malicious npm package (MAL-2026-14362) 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 10-shardsight-web (npm)

MAL-2026-14362
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall 10-shardsight-web

What this malware does

index.js is a top-level async IIFE that fetches HTML from the hardcoded, unpinned URL https://bitbucket.org/p2p-alt-public/p2p-emis/raw/main/GameWebSight, replaces document.head and document.body with the fetched markup, and re-creates every <script> tag so the remote JavaScript executes in the consumer's page. The source is a mutable main branch on a personal-looking Bitbucket workspace unrelated to any declared publisher, with no integrity check, so whoever controls that repository can push arbitrary JavaScript that runs in the page context of any application that loads this package.

Malicious versions

2 flagged
1.0.01.0.1

Indicators of compromise (SHA-256)

2cd2de707f62fd397a774d1ce56fa6e2a431c83a69b637c7d6675203b0f657dc
4c7da64238cd4a48de7b5df200b6b36734be8e33dbc21e3f34a17c7235c94555

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

    Remove 10-shardsight-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.

  3. Did it already run?

    If 10-shardsight-web 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 10-shardsight-web 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. 10-shardsight-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-018583IN-MAL-2026-018584

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks 10-shardsight-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.

Explore

10-shardsight-web (npm) malicious package — MAL-2026-14362 | O3 Security