Which versions of sotqa-test are malicious?

The following npm versions of sotqa-test are flagged malicious: 20.3.8. Treat any of these as compromised.

How do I remediate sotqa-test if I installed it?

sotqa-test establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed sotqa-test — how do I know if it already compromised me?

If sotqa-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 sotqa-test part of a known attack campaign?

Yes — sotqa-test is associated with the IN-MAL-2026-011516 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 sotqa-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 sotqa-test (version 20.3.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sotqa-test across your stack and pipelines.

Malicious package

sotqa-testnpm

sotqa-test is a confirmed malicious npm package (MAL-2026-12071) that opens a backdoor for remote access (malicious version 20.3.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in sotqa-test (npm)

MAL-2026-12071

Immediate action

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

npm uninstall sotqa-test

What this malware does

On require, sotqa-test loads bootstrap.js which reconstructs C2 hostnames from split-string arrays joined at runtime (oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev) with a DNS TXT covert-channel fallback under *.dl.well1.site resolvers (tin, tina, ldr, win subdomains), downloads a platform-specific native binary via https.get, writes it to /tmp or %TEMP% under a disguised filename (.cache<rand> on POSIX, dotnet_diag_<rand>.exe on Windows), chmods 0755, and spawns it detached via /bin/sh -c or cmd.exe. There is no hash or signature verification, endpoints are mutable, and both the delivery hosts and dropped-file names use cover-story naming (analytics, dotnet_diag). A second obfuscated dropper module lib/telemetry.js — presented as an Analytics SDK — resolves child_process via string concatenation ("child_"+"process"), assembles a base64 payload buffer, chmods the artifact 0755 using fs["chmod"+"Sync"], and spawns it detached with /bin/sh -c, providing a parallel execution surface.

Malicious versions

1 flagged

20.3.8

Indicators of compromise (SHA-256)

6980ae2860be6b9f343e9705a5415dc9ea13a81d285c1dce1f2f56b3dc989fbd

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for sotqa-test (version 20.3.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sotqa-test across your stack and pipelines.
If you installed it — respond
sotqa-test establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If sotqa-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 sotqa-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. sotqa-test on npm has been identified as a malicious package (version 20.3.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-011516

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks sotqa-test-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database