Which versions of chapters-core are malicious?

The following npm versions of chapters-core are flagged malicious: 9.999.999. Treat any of these as compromised.

How do I remediate chapters-core if I installed it?

chapters-core 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 chapters-core — how do I know if it already compromised me?

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

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

Malicious package

chapters-corenpm

chapters-core is a confirmed malicious npm package (MAL-2026-13752) that steals credentials and exfiltrates sensitive data (malicious version 9.999.999). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in chapters-core (npm)

MAL-2026-13752

Immediate action

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

npm uninstall chapters-core

What this malware does

The package registers preinstall/postinstall lifecycle scripts that execute poc.js on npm install. poc.js collects os.hostname(), os.userInfo().username, process.cwd(), and CI/CD attribution environment variables (GITHUB_REPOSITORY, GITHUB_ACTOR, GITHUB_RUN_ID, RUNNER_NAME, npm_config_registry, AWS_REGION, JENKINS_URL, and similar) and transmits them via DNS lookups and HTTP/HTTPS POST to a hardcoded Interactsh callback subdomain awfhvaksncnsxtcdjvmnhhqbt59dzenf8.oast.fun. The package name chapters-core at version 9.999.999 is shaped as a dependency-confusion squat of an internal package name, and poc.js additionally writes a marker file samsung-depconf-poc.json into the caller's working directory. Any self-labeling of the file as research does not alter the observed behavior: install-time collection of installer host identity and internal build-environment attribution and transmission to a hardcoded, non-first-party destination.

Malicious versions

1 flagged

9.999.999

Indicators of compromise (SHA-256)

e24d8bd29ee6c23e0f394b68bbc5b580614da4479a2462c10d61387da464b992

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

Campaign

IN-MAL-2026-017389

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks chapters-core-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

Explore

All malware advisories How O3 detects malware Vulnerability database