Which versions of @notrainer/nobtrainer-sdk are malicious?

The following npm versions of @notrainer/nobtrainer-sdk are flagged malicious: 1.0.2, 1.0.3, 1.0.4, 1.0.5. Treat any of these as compromised.

How do I remediate @notrainer/nobtrainer-sdk if I installed it?

@notrainer/nobtrainer-sdk 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 @notrainer/nobtrainer-sdk — how do I know if it already compromised me?

If @notrainer/nobtrainer-sdk 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.

How do I find @notrainer/nobtrainer-sdk across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @notrainer/nobtrainer-sdk (4 malicious versions).

Malicious package

@notrainer/nobtrainer-sdknpm

Advisory published Oct 29, 2026Updated Nov 2, 2026

@notrainer/nobtrainer-sdk is a confirmed malicious npm package (MAL-2026-18446) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.2, 1.0.3, 1.0.4…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @notrainer/nobtrainer-sdk (npm)

MAL-2026-18446

Immediate action

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

npm uninstall @notrainer/nobtrainer-sdk

What this malware does

Malicious package. @notrainer/nobtrainer-sdk is an npm package that exfiltrates sensitive data on the victim host to an attacker-controlled Discord webhook. The same Discord webhook endpoint (ID 1433690093175967776) is also used by the npm package @johnruff215-dev/solana-wallet-tracker, indicating both belong to a single actor/campaign. Classification: information stealer. The package provides no legitimate functionality, so all published versions are malicious. Full indicators are published at the reference below.

Malicious versions

4 flagged

1.0.21.0.31.0.41.0.5

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @notrainer/nobtrainer-sdk (4 malicious versions).
If you installed it — respond
@notrainer/nobtrainer-sdk 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 @notrainer/nobtrainer-sdk 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. @notrainer/nobtrainer-sdk on npm has been identified as a malicious package (versions 1.0.2, 1.0.3, 1.0.4, 1.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

wormsign · finder

Detect & block this

O3 blocks @notrainer/nobtrainer-sdk-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

Explore

All malware advisories How O3 detects malware Vulnerability database