Which versions of syft-acp-atoms are malicious?

The following npm versions of syft-acp-atoms are flagged malicious: 1.0.0, 14.8.68. Treat any of these as compromised.

How do I remediate syft-acp-atoms if I installed it?

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

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

Yes — syft-acp-atoms is associated with the IN-MAL-2026-013390, IN-MAL-2026-016543 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 syft-acp-atoms 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 syft-acp-atoms (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging syft-acp-atoms across your stack and pipelines.

Malicious package

syft-acp-atomsnpm

syft-acp-atoms is a confirmed malicious npm package (MAL-2026-10764) that opens a backdoor for remote access (malicious versions 1.0.0, 14.8.68). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in syft-acp-atoms (npm)

MAL-2026-10764

Immediate action

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

npm uninstall syft-acp-atoms

What this malware does

The syft-acp-atoms package was published to the npm registry by user 'ada8877' (maintainer email [email protected]) as part of a dependency-confusion / reconnaissance campaign. The package name mimics the 'syft-acp' internal/private package naming convention (an ACP component library) of a target organization, so that a misconfigured resolver installs this public lookalike instead of the intended private dependency.

The package declares a preinstall hook ("npm install @sentry/node && node examples/verify.js") that executes automatically at npm install time, before any application code runs. The bundled examples/verify.js initializes the @sentry/node client against a hardcoded, attacker-controlled Sentry DSN with sendDefaultPii enabled, resolves the installing host's public egress IP address by requesting Cloudflare's /cdn-cgi/trace endpoint (using a spoofed desktop-browser User-Agent to bypass bot challenges), then deliberately triggers a runtime exception and captures it. Flushing the event beacons the collected host telemetry (public IP plus Sentry default PII such as hostname, OS username and runtime/environment metadata) to the attacker's Sentry ingest endpoint at o4510485815754752.ingest.us.sentry.io.

Each impersonated namespace in the campaign beacons to a distinct Sentry project ID, letting the operator attribute successful installs to specific victim organizations — behaviour consistent with a dependency-confusion reconnaissance beacon rather than legitimate error monitoring. The install-time payload is byte-for-byte identical to the earlier 'click2ai' campaign, sharing the same Sentry organization (o4510485815754752) and a related ProtonMail maintainer identity, and differs only in the package name and target DSN. This package's beacon targets Sentry project 4511744089718784.

On npm install, the package's postinstall hook (node./beacon.js) collects the installer's hostname, OS username, and current working directory via os.hostname(), os.userInfo(), and process.cwd(), hex-encodes them, and transmits them as a query string to https://exzotiqq.com/ via https.get. The package ships no library code — the declared main: index.js is absent from the tarball — so the only effect of installing the package is to run the beacon. Behavior is consistent with a reconnaissance / dependency-confusion probe.

Malicious versions

2 flagged

1.0.014.8.68

Indicators of compromise (SHA-256)

7ed8acd69ab483ef58fdeea92d871264713661755e025eb16d7f3b34be02f9b4

74ddca6430f87ddf8a19eed0ed269e147b577c055d399bec7ca1fed6fa1d75f1

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

Campaign

IN-MAL-2026-013390IN-MAL-2026-016543

References

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks syft-acp-atoms-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