Which versions of ac_semantic-ui_ts are malicious?

The following npm versions of ac_semantic-ui_ts are flagged malicious: 99.99.100. Treat any of these as compromised.

How do I remediate ac_semantic-ui_ts if I installed it?

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

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

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

Malicious package

ac_semantic-ui_tsnpm

Malicious code in ac_semantic-ui_ts (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5435

Immediate action

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

npm uninstall ac_semantic-ui_ts

What this malware does

package.json declares a postinstall hook that runs canary.js, which issues an HTTP GET to bare IP 157.230.17.236 on port 80 with query parameters including os.hostname(), the package name and version, a nonce, and a lifecycle phase. The package name ac_semantic-ui_ts paired with the inflated version 99.99.100 is the canonical dependency-confusion shape — designed to win resolution over an internal/private registry entry of the same name. Any installer who resolves this package from public npm silently transmits their host identifier to an unencrypted, hardcoded, non-publisher endpoint with no opt-in. The README self-describes as an 'authorized benign dependency-confusion canary,' but the supply-chain mechanism — install-time exfiltration of installer host metadata to a third-party IP — is identical to a malicious dependency-confusion beacon, and any installer who pulls this unintentionally has their hostname leaked.

Malicious versions

1 flagged

99.99.100

Indicators of compromise (SHA-256)

f8b97f7d3e69494d0415e13aec8d9d51ce1f5912d8c1de45a1e563e2d1b01d3d

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

Campaign

IN-MAL-2026-005008

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ac_semantic-ui_ts-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