Which versions of captainindia are malicious?

The following npm versions of captainindia are flagged malicious: 1.1.2, 2.0.0. Treat any of these as compromised.

How do I remediate captainindia if I installed it?

Remove captainindia from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed captainindia — how do I know if it already compromised me?

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

Yes — captainindia is associated with the GHSA-j4pr-j9jm-rj9c, IN-MAL-2026-010450, RLMA-2026-05505, RLUA-2026-06104 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 captainindia 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 captainindia (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging captainindia across your stack and pipelines.

Malicious package

captainindianpm

captainindia is a confirmed malicious npm package (MAL-2026-10297) that executes malicious code on install (malicious versions 1.1.2, 2.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in captainindia (npm)

MAL-2026-10297

Immediate action

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

npm uninstall captainindia

What this malware does

The package was found to contain malicious code or consuming dependency that contains 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

2 flagged

1.1.22.0.0

Indicators of compromise (SHA-256)

70e90ba63ec7e9e28b20dc41d6ef50ca61a0e99fbacf0d921ed6a0387f1ce9ba

733cf02dcdf94f8882c708ffcafec943cc986ee2909b6c6800ee9e34c8b8fccb

448fba185302fda5be2244d01efb8a491be8fa964a94d624b3575594f9ae262a

0e724a6813536a14591457ceb6996005ee07ce2f48d9b70576287c9be57ee5ad

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for captainindia (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging captainindia across your stack and pipelines.
If you installed it — respond
Remove captainindia from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If captainindia 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 captainindia 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. captainindia on npm has been identified as a malicious package (versions 1.1.2, 2.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-j4pr-j9jm-rj9cIN-MAL-2026-010450RLMA-2026-05505RLUA-2026-06104

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks captainindia-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database