Which versions of designstudiouiux are malicious?

The following npm versions of designstudiouiux are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate designstudiouiux if I installed it?

designstudiouiux 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 designstudiouiux — how do I know if it already compromised me?

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

Yes — designstudiouiux is associated with the GHSA-4cm9-fpp9-mjwx 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 designstudiouiux 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 designstudiouiux (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging designstudiouiux across your stack and pipelines.

Malicious package

designstudiouiuxnpm

Malicious code in designstudiouiux (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190955

Immediate action

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

npm uninstall designstudiouiux

What this malware does

The package designstudiouiux 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.1

Indicators of compromise (SHA-256)

0fd8a6a7d5cef9c71c739d05d4e75644f2a303bcae6db5f3b32680d2fc562785

b36c1311e04a95981cee366a30d6aee0dd7f15421166231abbba74f617035927

b78695bd1f17a469d96c2e9feac43a67130dded2d7c8ef89bf8bf168b23b316e

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 designstudiouiux (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging designstudiouiux across your stack and pipelines.
If you installed it — respond
designstudiouiux 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 designstudiouiux 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 designstudiouiux 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. designstudiouiux on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-4cm9-fpp9-mjwx

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks designstudiouiux-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