Which versions of ms_aidc_com_tw are malicious?

The following npm versions of ms_aidc_com_tw are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate ms_aidc_com_tw if I installed it?

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

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

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

Malicious package

ms_aidc_com_twnpm

ms_aidc_com_tw is a confirmed malicious npm package (MAL-2026-13828) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ms_aidc_com_tw (npm)

MAL-2026-13828

Immediate action

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

npm uninstall ms_aidc_com_tw

What this malware does

The package ms_aidc_com_tw ships only an index.html that renders a fake Cloudflare Turnstile 'security verification' page. On Turnstile completion, heavily obfuscated JavaScript (obfuscator.io-style rotating string array _0x59f1, RC4/base64 decoder _0x2020, self-defending anti-debug checks) assembles a URL to login.microsoftonline.com, copies the current page's query-string parameters onto it, and calls window.location.replace to hand the victim off to Microsoft's real login with attacker-controlled parameters preserved — the standard adversary-in-the-middle / OAuth-consent phishing relay pattern. The package name impersonates a Microsoft-branded Taiwanese corporate domain (ms.aidc.com.tw). The obfuscation exists solely to conceal the phishing destination and the parameter-relay logic from casual review. The npm registry is being abused as hosting infrastructure for a Microsoft 365 credential-harvesting landing page.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

926b2f1c75043aede24fbf0e72194caddfa40433659e3891da83fdd7c7eac8b7

b12bdd45f103beeee602be82a07277a3f0cb842ec3a9829e904911fe37bd2fd5

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

Campaign

GHSA-2fg7-gfq8-c24gIN-MAL-2026-017546

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ms_aidc_com_tw-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