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

nim-submit-for-testnpm

Advisory published Updated

nim-submit-for-test is a confirmed malicious npm package (MAL-2026-5570) that steals credentials and exfiltrates sensitive data (malicious version 2.2.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in nim-submit-for-test (npm)

MAL-2026-5570
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall nim-submit-for-test

What this malware does

On npm install, the package's postinstall hook executes lib/_compiler.js, which spawns a detached Node process that collects host identity (hostname, username, cwd, IP addresses, npm registry) and the names of environment variables matching NPM|NODE|CI|JENKINS|GIT|BUILD|RUNNER|DOCKER|KUBE|REGISTRY, then POSTs them via https.request to a hardcoded DingTalk webhook (oapi.dingtalk.com/robot/send) with an embedded access token. Before sending, the script checks the installer's username and hostname against an evasion list ('sandbox','malware','analyst','cuckoo','analysis','sample') and exits silently when matched, to avoid running in security analysis environments. The combination of automatic install-time execution, host/CI metadata collection, hardcoded attacker-controlled webhook, and analyst-environment evasion is a clear supply-chain exfiltration beacon.

Malicious versions

1 flagged
2.2.0

Indicators of compromise (SHA-256)

2bf75301042574897cc2f4bd8f3b8939fe4ac7a958f2cfe2404bbbee149797d0
77bfef43e57cee7068599b0d1af2fd6b5400e7298aa9833fdffda514a28eeeb2

Detection & response playbook

Credential / info stealer

  1. Find it

    Search your lockfiles and build artifacts for nim-submit-for-test (version 2.2.0).

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-005471IN-MAL-2026-005472

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks nim-submit-for-test-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
nim-submit-for-test (npm) malicious package — MAL-2026-5570 | O3 Security