Which versions of aitable-workflow-server are malicious?

The following npm versions of aitable-workflow-server are flagged malicious: 9.9.9. Treat any of these as compromised.

How do I remediate aitable-workflow-server if I installed it?

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

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

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

Malicious package

aitable-workflow-servernpm

aitable-workflow-server is a confirmed malicious npm package (MAL-2026-13437) that opens a backdoor for remote access (malicious version 9.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in aitable-workflow-server (npm)

MAL-2026-13437

Immediate action

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

npm uninstall aitable-workflow-server

What this malware does

The package's dist/index.js contains code combining OS command execution (ping) with outbound HTTP POST requests, a pattern consistent with host reconnaissance and data beaconing to an external endpoint. The package name resembles a legitimate workflow tool but the shipped bundle is a small file whose only functionality is issuing ping commands and POSTing results outward, with no code implementing the advertised workflow-server functionality. Version 9.9.9 is a version-number pattern frequently used in dependency-confusion attacks targeting internal package names.

Malicious versions

1 flagged

9.9.9

Indicators of compromise (SHA-256)

c9fd48b8764ece5b776ed22530ce8c86ffef1093f52fc74ab00fbb740817af82

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

Campaign

IN-MAL-2026-016684

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks aitable-workflow-server-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