Which versions of dgxeon-soket are malicious?

The following npm versions of dgxeon-soket are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate dgxeon-soket if I installed it?

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

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

Yes — dgxeon-soket is associated with the GHSA-838q-63vp-c27h, RLMA-2026-01243, RLUA-2026-01742 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 dgxeon-soket 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 dgxeon-soket (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dgxeon-soket across your stack and pipelines.

Malicious package

dgxeon-soketnpm

Malicious code in dgxeon-soket (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1074

Immediate action

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

npm uninstall dgxeon-soket

What this malware does

The package dgxeon-soket 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

1.0.0

Indicators of compromise (SHA-256)

7814fe539784c04cc6450ee43c3902eab63d439030fa47b7678ccb32e8655119

3bc1fe5368b07366735c8e9f8163262c8e77e1be50c66c9158459b89cf348cac

a10a16f90f3af9936e01050ec75ed13a7bbd10e33f2389e798a8d2c0a02c55bb

f0214356fa5582295a6509c187ae89be4a8ac3c7b7a943685c8ad9f9dcee813a

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

Campaign

GHSA-838q-63vp-c27hRLMA-2026-01243RLUA-2026-01742

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks dgxeon-soket-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