Which versions of nim-submit-for-test are malicious?

The following npm versions of nim-submit-for-test are flagged malicious: 2.2.0. Treat any of these as compromised.

How do I remediate nim-submit-for-test if I installed it?

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.

I already installed nim-submit-for-test — how do I know if it already compromised me?

If nim-submit-for-test was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is nim-submit-for-test part of a known attack campaign?

Yes — nim-submit-for-test is associated with the IN-MAL-2026-005471, IN-MAL-2026-005472 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find nim-submit-for-test across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for nim-submit-for-test (version 2.2.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nim-submit-for-test across your stack and pipelines.

Malicious package

nim-submit-for-testnpm

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

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for nim-submit-for-test (version 2.2.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nim-submit-for-test across your stack and pipelines.
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.
Did it already run?
If nim-submit-for-test was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks nim-submit-for-test before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

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

npmjs.com

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