MalwarePublished 13 Jul 2026Updated 24 Sep 2026

captainindia (npm) · Malicious Code

Affects captainindiaSource GCVE Database

Malicious package : remove captainindia and rotate any secrets on hosts that installed it.

Data as of 26 Oct 2026, 15:56 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-10297

What to do

Remove captainindia from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npmcaptainindia	Affected =2.0.0 =1.1.2	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

The npm package 'captainindia' was found to contain malicious code or dependencies with malicious code. Systems with this package installed should be considered fully compromised. Immediate removal of the package and rotation of all secrets and keys from a different, uncompromised computer is strongly advised. Due to the potential full control gained by attackers, removing the package may not fully eradicate the malicious presence.

Impact

Any computer with the 'captainindia' package installed or running is considered fully compromised. Attackers may have gained full control over the system, risking exposure or theft of all secrets and keys stored on the device. This represents a critical security risk with potential for extensive damage or data loss.

Defensive guidance

Remove the 'captainindia' package immediately. Rotate all secrets and keys stored on the compromised computer from a different, secure computer. Because full control of the system may have been obtained by attackers, additional forensic analysis and remediation steps may be necessary beyond package removal.

Summary

The 'captainindia' package on npm includes malicious code or depends on components that are malicious. Installation or execution of this package compromises the host system, potentially allowing attackers full control. The compromise is severe enough that all stored secrets and keys on the affected system should be rotated immediately from a secure environment. Removal of the package alone does not guarantee complete remediation due to possible persistence mechanisms.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Sep 2026, 17:17 UTC

Technical details

References

Community reviews