Which versions of itc-actors-api are malicious?

The following npm versions of itc-actors-api are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate itc-actors-api if I installed it?

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

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

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

Malicious package

itc-actors-apinpm

Malicious code in itc-actors-api (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4589

Immediate action

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

npm uninstall itc-actors-api

What this malware does

The package contains callback.js which collects host identifiers and user information (os.hostname(), os.userInfo(), os.platform(), cwd) and transmits them via an HTTPS request. The file structures the collected data with fields like hostname, username, and cwd — the canonical reconnaissance-beacon shape used by dependency-confusion / supply-chain reconnaissance campaigns. The package name and 99.0.0 version (a high-version-number pattern typical of dependency-confusion attacks targeting internal package names) further corroborate malicious intent. Installing or loading this package leaks identifying information about the installer's machine to an external endpoint.

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

22687e1f7601dde1753d3775925d62d040892631394937e56e9b9fba74fb85c6

71febd3f98de8965afd1151fd7d6f363a4747fc8978e0d3a7e82d8f68d5aaf69

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

Campaign

IN-MAL-2026-004653IN-MAL-2026-004654

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks itc-actors-api-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