Which versions of strict-engine-peer are malicious?

The following npm versions of strict-engine-peer are flagged malicious: 1.0.0, 22.18.0. Treat any of these as compromised.

How do I remediate strict-engine-peer if I installed it?

Remove strict-engine-peer 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 network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Is strict-engine-peer part of a known attack campaign?

Yes — strict-engine-peer is associated with the IN-MAL-2026-006768, IN-MAL-2026-006767 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

Can O3 Security detect strict-engine-peer in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking strict-engine-peer and packages like it before any post-install script runs.

Malicious package

strict-engine-peernpm

Malicious code in strict-engine-peer (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5898

Immediate action

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

npm uninstall strict-engine-peer

What this malware does

On npm install, the package's preinstall hook (preinstall: node index.js in package.json) executes index.js, which reads the installer's project directory via process.env.INIT_CWD, takes its basename as safeProjectName, and POSTs a JSON payload containing that name and a timestamp to a hardcoded callback URL https://deepbounty.dd06-dev.fr/cb/d9b7e171-33a4-49c7-aa79-c95794030d3b. The package self-describes as a 'Security PoC for Bug Bounty' / 'Harmless dependency confusion PoC', and the name strict-engine-peer is consistent with squatting an internal/private package name on the public npm registry. Any developer or build system that resolves this package — typically by accident, via dependency confusion against an internal package of the same name — silently discloses the existence and name of an internal project to the third-party endpoint. The 'research' framing does not change the installer-side impact: unconsented network beacon at install time, leaking organizational metadata to an attacker-controlled host.

Malicious versions

2 flagged

1.0.022.18.0

Indicators of compromise (SHA-256)

0913b30a168bfed09d3c5ae59aeaf6a305a395f86516fb1fb8ece60bb95904de

ac925bb7b76abeaac88261c3f69c48a2940832889dd660b9cdd8af443b0c1183

Frequently asked questions

No. strict-engine-peer on npm has been identified as a malicious package (versions 1.0.0, 22.18.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006768IN-MAL-2026-006767

References

Credits

Amazon Inspector · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection