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?

Remove ac_semantic-ui_ts from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

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.

Can O3 Security detect ac_semantic-ui_ts in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking ac_semantic-ui_ts and packages like it before any post-install script runs.

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

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

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection