Which versions of engin1 are malicious?

The following npm versions of engin1 are flagged malicious: 1.3.99. Treat any of these as compromised.

How do I remediate engin1 if I installed it?

engin1 establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

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

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

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

Malicious package

engin1npm

engin1 is a confirmed malicious npm package (MAL-2026-16215) that opens a backdoor for remote access (malicious version 1.3.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in engin1 (npm)

MAL-2026-16215

Immediate action

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

npm uninstall engin1

What this malware does

The package's main entrypoint (index.js) invokes an initializer at top level that spawns loader.js as a detached background Node process on every require/import. loader.js issues an HTTPS GET to https://api.npoint.io/24c25d5f5fcbb0992a4f, base64-decodes the JSON code field, and passes the decoded string to new Function(require, __dirname, __filename, module, exports,...), executing attacker-controlled JavaScript with full Node privileges as the installing user. The endpoint URL is stored in a variable named API_KEY to disguise its nature, and the manifest/README advertise a runtime/system-info utility with a getRuntimeInfo() API that does not exist in the shipped code. The api.npoint.io document is attacker-mutable, unauthenticated, and unpinned, so whoever controls that bin controls what runs on any host importing this package.

Malicious versions

1 flagged

1.3.99

Indicators of compromise (SHA-256)

1e843727c643c5d966acaa66461f7e392813a4284cd8181b4bb9b24ddfb8447a

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for engin1 (version 1.3.99). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging engin1 across your stack and pipelines.
If you installed it — respond
engin1 establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If engin1 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 engin1 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. engin1 on npm has been identified as a malicious package (version 1.3.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020083

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks engin1-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database