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

nim-submit-for-testnpm

Malicious code in nim-submit-for-test (npm) Remove it immediately and rotate any exposed credentials.

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

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

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection
nim-submit-for-test (npm) malicious package — MAL-2026-5570 | O3 Security