Which versions of dashboard-empty-state are malicious?

The following npm versions of dashboard-empty-state are flagged malicious: 1.0.3. Treat any of these as compromised.

How do I remediate dashboard-empty-state if I installed it?

dashboard-empty-state is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed dashboard-empty-state — how do I know if it already compromised me?

If dashboard-empty-state 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 dashboard-empty-state part of a known attack campaign?

Yes — dashboard-empty-state is associated with the GHSA-c43q-4447-wm7m, RLMA-2025-06107 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 dashboard-empty-state 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 dashboard-empty-state (version 1.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dashboard-empty-state across your stack and pipelines.

Malicious package

dashboard-empty-statenpm

Malicious code in dashboard-empty-state (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190954

Immediate action

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

npm uninstall dashboard-empty-state

What this malware does

The package dashboard-empty-state was found to contain malicious code.

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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

1.0.3

Indicators of compromise (SHA-256)

ddb34ca8b91d29cb7e8d97d0b2ecbe4f274a247c851a27e59df4131f4c6cee1f

b00545cf1acf95f278f2b1fca78d8c3df406a74600585630c0ff6c6c526b53b4

9390386244388769ef93eb09527ec4a827fb8327f48952954b5517f0671a3353

aca7b8a009ed92a9ba287707791336e2e998c0796cd00ea453eed0eb63f7a038

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dashboard-empty-state (version 1.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dashboard-empty-state across your stack and pipelines.
If you installed it — respond
dashboard-empty-state is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If dashboard-empty-state 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 dashboard-empty-state 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. dashboard-empty-state on npm has been identified as a malicious package (version 1.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-c43q-4447-wm7mRLMA-2025-06107

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks dashboard-empty-state-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring