Which versions of specials-mvno-client are malicious?

The following npm versions of specials-mvno-client are flagged malicious: 20.9.8. Treat any of these as compromised.

How do I remediate specials-mvno-client if I installed it?

specials-mvno-client 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 specials-mvno-client — how do I know if it already compromised me?

If specials-mvno-client 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 specials-mvno-client part of a known attack campaign?

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

Malicious package

specials-mvno-clientnpm

specials-mvno-client is a confirmed malicious npm package (MAL-2026-12044) that steals credentials and exfiltrates sensitive data (malicious version 20.9.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in specials-mvno-client (npm)

MAL-2026-12044

Immediate action

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

npm uninstall specials-mvno-client

What this malware does

index.js requires bootstrap.js at module load, which fetches an opaque platform-specific binary from string-split Cloudflare Workers hosts (oob-worker.cf99-9b3.workers.dev) and *.dl.well1.site subdomains, writes it to /var/tmp or %TEMP% under disguised filenames (.cache<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmods 0755, and spawns it detached via spawn('/bin/sh', ['-c', <path>+' &']) or cmd.exe /c start /b. Host names are assembled via array.join to defeat literal string matching. A DNS-TXT fallback channel resolves TXT records under c.<domain> and N.<domain>, concatenating base64 chunks to deliver code when HTTPS is unavailable. The module is cloaked with telemetry-shaped naming (.analytics_state state file, comments describing 'CDN negotiation') and honors DISABLE_TELEMETRY / DO_NOT_TRACK / ANALYTICS_OPT_OUT environment variables to skip execution on scrutinized hosts. The fetched bytes are not publisher-hosted, are opaque, and are executed on every install/require of the package.

Malicious versions

1 flagged

20.9.8

Indicators of compromise (SHA-256)

852448e1055feb834486a41aaf7e1a621a52fc4e9a496f34c0bde833e751434b

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 specials-mvno-client (version 20.9.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging specials-mvno-client across your stack and pipelines.
If you installed it — respond
specials-mvno-client 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 specials-mvno-client 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 specials-mvno-client 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. specials-mvno-client on npm has been identified as a malicious package (version 20.9.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-011494

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks specials-mvno-client-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