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

home-sections-web-uinpm

Malicious code in home-sections-web-ui (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10443
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall home-sections-web-ui

What this malware does

package.json declares the dependency ltidisafe as a direct tarball URL (https://storage.googleapis.com/lscunpentest/pack_ux_foundry.tgz) hosted on an anonymous Google Cloud Storage bucket unrelated to any known publisher. Installing this package causes npm to fetch and install arbitrary, attacker-mutable JavaScript from that URL into the installer's dependency tree, bypassing the npm registry entirely. Package metadata is consistent with a throwaway lure: nonsensical author (lslsls), placeholder description (lspodcc), version 99.9.9, and a bucket name (lscunpentest) suggesting pen-test / dependency-confusion tooling. The fetched tarball's contents are not pinned by hash and can be swapped at any time by whoever controls the bucket.

Malicious versions

1 flagged
99.9.9

Indicators of compromise (SHA-256)

2e6c206f8844e1ff870876bc1ac8cdf2b10ee2c36caf61883eb5a8f03caa5405

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 home-sections-web-ui (version 99.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging home-sections-web-ui across your stack and pipelines.

  2. If you installed it — respond

    Remove home-sections-web-ui 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 home-sections-web-ui 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 home-sections-web-ui 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. home-sections-web-ui on npm has been identified as a malicious package (version 99.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010240

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks home-sections-web-ui-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.

home-sections-web-ui (npm) malicious package — MAL-2026-10443 | O3 Security