Which versions of agents-a365-runtime are malicious?

The following npm versions of agents-a365-runtime are flagged malicious: 1.3.8. Treat any of these as compromised.

How do I remediate agents-a365-runtime if I installed it?

agents-a365-runtime 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 agents-a365-runtime — how do I know if it already compromised me?

If agents-a365-runtime 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 agents-a365-runtime part of a known attack campaign?

Yes — agents-a365-runtime is associated with the GHSA-98v9-9pjp-6p9m 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 agents-a365-runtime 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 agents-a365-runtime (version 1.3.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging agents-a365-runtime across your stack and pipelines.

Malicious package

agents-a365-runtimenpm

Malicious code in agents-a365-runtime (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3149

Immediate action

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

npm uninstall agents-a365-runtime

What this malware does

Malicious npm package published by threat actor "raya4321" as part of a coordinated typosquatting campaign impersonating Apple internal infrastructure services (authentication, PKI, telemetry, CloudKit, and cloud infrastructure). All packages in this campaign execute credential-theft payloads during npm installation via preinstall or postinstall lifecycle hooks.

Trigger: preinstall. Executes ms_audit.sh on install, performing Kubernetes pod infiltration: reads Kubernetes service account tokens from /var/run/secrets/kubernetes.io/serviceaccount/token, captures the pod namespace, and scans environment variables for KUBE/SERVICE/API/PORT/PROTO patterns; exfiltrates to https://webhook.site/42fb16cd-cddc-4a22-a7aa-ea6505ede8d6. The package also bundles pwn.sh, which hunts for npm/GitHub authentication tokens (NPM_TOKEN, NODE_AUTH_TOKEN, GITHUB_TOKEN, NPM_AUTH_TOKEN) in the environment and ~/.npmrc, then uses any found token to publish a trojanized version of apple-app-store-server-library to the npm registry (supply chain attack), and exfiltrates results to https://webhook.site/85f78e76-dc73-4cb5-a65c-27f2c10db591.

The package agents-a365-runtime was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.3.8

Indicators of compromise (SHA-256)

d8bee41ee6df8fa75970642190e1baef5059a43a36b9a08d935c67feaeac8bb3

2bfd07a40e1e8923d801c644492c02b636853e54d2f010938baa01e3f15a8570

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

Campaign

GHSA-98v9-9pjp-6p9m

References

github.com

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks agents-a365-runtime-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