Which versions of @gad360/apothem are malicious?

The following npm versions of @gad360/apothem are flagged malicious: 1.1.0. Treat any of these as compromised.

How do I remediate @gad360/apothem if I installed it?

@gad360/apothem 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 @gad360/apothem — how do I know if it already compromised me?

If @gad360/apothem 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 @gad360/apothem part of a known attack campaign?

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

Malicious package

@gad360/apothemnpm

Malicious code in @gad360/apothem (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4391

Immediate action

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

npm uninstall @gad360/apothem

What this malware does

The package's package.json declares a postinstall hook ("postinstall": "node install.js") that runs install.js automatically on npm install. install.js requires fs, os, https, and child_process, reads environment variables and host metadata (process.env, process.platform, process.arch, os.tmpdir, fs.readFileSync), and issues an https.get to the hardcoded endpoint https://ahmedgad.com. The combination of a hardcoded non-publisher destination with environment/system reads inside a lifecycle script is the canonical install-time exfiltration shape. The destination is unrelated to any documented vendor SDK or runtime CDN, and there is no version pinning, hash verification, or build-from-source justification for the network call.

Malicious versions

1 flagged

1.1.0

Indicators of compromise (SHA-256)

4f5e509ba6aa2f781391f03ff37ea8005440c1d1106391bdfa91abae06336ad3

ad5f5b336ec6522037b3042e4f0adf68e9cd2e0fb4d94789f9ef5b1bc158b912

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

Campaign

IN-MAL-2026-003662IN-MAL-2026-003663

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @gad360/apothem-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