NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

sodel-pychnpm

Advisory published Updated

sodel-pych is a confirmed malicious npm package (MAL-2026-6062) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.121, 1.0.122). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in sodel-pych (npm)

MAL-2026-6062
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall sodel-pych

What this malware does

The package ships several files whose names and contents suggest a non-trivial install-time and runtime footprint: a postinstall script (scripts/postinstall-agent.mjs) that performs network I/O including a ping/GET against an identifier-bearing endpoint, a relay server (dist/relayServer.js) with multiple ping invocations, a Discord relay upload module (dist/discordRelayUpload.js) combining base64 decoding with POST calls, a Hugging Face credentials module (dist/hfCredentials.js) using base64-decoded values, and a secret-scan startup audit (dist/secretScan/agentStartupAudit.js) that fetches huggingface.co endpoints. The combination of a postinstall agent, a Discord upload path, base64-encoded data in deployment defaults, and credential/secret handling is consistent with either (a) a legitimate ML/agent tooling package that talks to Hugging Face and uses Discord for notifications, or (b) a credential-relay/exfiltration tool. The evidence available here is keyword-level pattern matches without traced execution paths, so intent cannot be determined from this data alone. A human reviewer should inspect scripts/postinstall-agent.mjs to confirm what runs on npm install, dist/discordRelayUpload.js to confirm whether installer-side data is shipped to Discord, and dist/hfCredentials.js to confirm whose credentials are read.

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

2 flagged
1.0.1211.0.122

Indicators of compromise (SHA-256)

95b8b8f54c9c2a4fa965e4a7fe7ea9c8f8ef1b5bcdd4cc1da7354d0ce2e8842f
c7d67bcaf42f4ef050a6b824dfbc2f711d6820f7b3b1140d211110f390e512fa
e4271fff06c918ff0843a3ecbe8b91ef905d89625bde23a47c44d0ca6f3a829d

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for sodel-pych (2 malicious versions).

  2. If you installed it — respond

    sodel-pych 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.

  3. Did it already run?

    If sodel-pych was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. sodel-pych on npm has been identified as a malicious package (versions 1.0.121, 1.0.122 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-4cgm-w872-8q5gIN-MAL-2026-009441IN-MAL-2026-009442

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Explore

sodel-pych (npm) malicious package — MAL-2026-6062 | O3 Security