Which versions of socket-dgxeon are malicious?

Every published version of socket-dgxeon on npm is considered malicious. Remove the package entirely.

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

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

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

Yes — socket-dgxeon is associated with the GHSA-rjr7-mc49-vw8f 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 socket-dgxeon 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 socket-dgxeon (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging socket-dgxeon across your stack and pipelines.

Malicious package

socket-dgxeonnpm

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

MAL-2026-1078

Immediate action

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

npm uninstall socket-dgxeon

What this malware does

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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

0f36366d3dd38134f3c8176992483c8c67f2e502ca9b774a4ea5a3fc2d428efc

b6b1cdce1957669bd7cca7bb7c90b018a87fad6ed9ea49b4874f127272f0c00d

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

Campaign

GHSA-rjr7-mc49-vw8f

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

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