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

@web-3d-tool/sdknpm

Malicious code in @web-3d-tool/sdk (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4465
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @web-3d-tool/sdk

What this malware does

@web-3d-tool/sdk is a near-empty package (trivial 35-byte index.js, empty author/description metadata) whose only effect on install is to pull in a dependency declared as a raw tarball URL: "ltidisafe": "https://ltidi.storage.googleapis.com/depenconf/ltidisafe-2.3.1.tgz" (package.json line 9). The bucket ltidi.storage.googleapis.com is unrelated to the @web-3d-tool namespace, is not a versioned npm registry artifact, and the bucket owner can mutate the served tarball at any time without changing this package's version. Any lifecycle hooks (preinstall/install/postinstall) inside the fetched tarball execute on npm install of this package, giving the bucket owner arbitrary code execution on the installer's machine. The combination of hollow lure package + tarball-URL dependency + unrelated anonymous storage bucket + missing publisher metadata is the namespace-abuse dropper shape — the package itself is not the payload, the resolved dependency is.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged
99.9.1

Indicators of compromise (SHA-256)

a1e96a726cf0732113215b2026a7a59fc6bf471f86d34153fea3a0e32b275fb5
e5dafe4c74a548d3a30151bc3624fa1017641519dcae1b19294c62a725b5f49a
9d4f9fb87e60635dd4d4a606a703c86ab5b5de333e94c69fc01ca97d689cea0d

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 @web-3d-tool/sdk (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @web-3d-tool/sdk across your stack and pipelines.

  2. If you installed it — respond

    Remove @web-3d-tool/sdk 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 @web-3d-tool/sdk 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 @web-3d-tool/sdk 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. @web-3d-tool/sdk on npm has been identified as a malicious package (version 99.9.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-003434IN-MAL-2026-003435GHSA-qmfq-m796-v557

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @web-3d-tool/sdk-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
@web-3d-tool/sdk (npm) malicious package — MAL-2026-4465 | O3 Security