Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

test__123q2npm

Advisory published Updated

test__123q2 is a confirmed malicious npm package (MAL-2026-15638) that steals credentials and exfiltrates sensitive data (malicious version 2.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in test__123q2 (npm)

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

What this malware does

On npm install, the package's postinstall script sweeps the installer's home directory for crypto wallet and credential material and uploads it to an attacker-controlled Telegram bot. Targets include browser wallet extension profiles for MetaMask (nkbihfbeogaeaoehlefnkodbefgpgknn), Phantom, Trust, Coinbase, OKX, Rabby, Keplr, TronLink, Ronin, Solflare and Exodus; desktop wallets Exodus, Atomic, Electrum, Bitcoin Core (wallet.dat), Ledger Live, Trezor Suite, Wasabi, Sparrow, Guarda, Coinomi and Jaxx; and files under Desktop, Documents, Downloads and Projects matching mnemonic/seed/bip39/privatekey keywords plus.env,.npmrc,.netrc, id_rsa and ~/.aws material. Collected files are tarballed via the tar dependency and POSTed as a document to a hardcoded Telegram Bot API endpoint (https://api.telegram.org/bot<BOT_TOKEN>/sendDocument); the destination is not user-configurable. The package name and version carry no legitimate functionality that would justify this behavior.

Malicious versions

1 flagged
2.1.1

Indicators of compromise (SHA-256)

1b08920ddaa70b578792ec7097f9d47047bdfe436a44475ed8274037ce6d6386

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for test__123q2 (version 2.1.1).

  2. If you installed it — respond

    test__123q2 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 test__123q2 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. test__123q2 on npm has been identified as a malicious package (version 2.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019306

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks test__123q2-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

test__123q2 (npm) malicious package — MAL-2026-15638 | O3 Security