Which versions of dubbo-js-private-workspace are malicious?

The following npm versions of dubbo-js-private-workspace are flagged malicious: 999.0.104. Treat any of these as compromised.

How do I remediate dubbo-js-private-workspace if I installed it?

Remove dubbo-js-private-workspace 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.

I already installed dubbo-js-private-workspace — how do I know if it already compromised me?

If dubbo-js-private-workspace 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 dubbo-js-private-workspace part of a known attack campaign?

Yes — dubbo-js-private-workspace is associated with the GHSA-fhq4-8wqq-qjw8, RLMA-2026-01266 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 dubbo-js-private-workspace 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 dubbo-js-private-workspace (version 999.0.104). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dubbo-js-private-workspace across your stack and pipelines.

Malicious package

dubbo-js-private-workspacenpm

Malicious code in dubbo-js-private-workspace (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192586

Immediate action

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

npm uninstall dubbo-js-private-workspace

What this malware does

The package dubbo-js-private-workspace 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.

Malicious versions

1 flagged

999.0.104

Indicators of compromise (SHA-256)

0fec531b3fbbd440c39263f7858420eb9c1d6cfdfa732c54367be5f4d0213c83

5d7718e849fa01a112b317438650757b783681fbb3361ec73154005719f6f892

e18bcf2ca363aa9cc1ce88d5a649b0fd9d98e4d3ca2ee827c9b6a820729f6157

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dubbo-js-private-workspace (version 999.0.104). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dubbo-js-private-workspace across your stack and pipelines.
If you installed it — respond
Remove dubbo-js-private-workspace 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.
Did it already run?
If dubbo-js-private-workspace 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 dubbo-js-private-workspace 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. dubbo-js-private-workspace on npm has been identified as a malicious package (version 999.0.104 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-fhq4-8wqq-qjw8RLMA-2026-01266

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks dubbo-js-private-workspace-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