Which versions of express-initial are malicious?

The following npm versions of express-initial are flagged malicious: 12.1.9, 12.1.10. Treat any of these as compromised.

How do I remediate express-initial if I installed it?

Remove express-initial 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 express-initial — how do I know if it already compromised me?

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

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

Malicious package

express-initialnpm

Malicious code in express-initial (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6543

Immediate action

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

npm uninstall express-initial

What this malware does

package.json declares "postinstall": "node index.js", so npm install express-initial automatically runs the package's main script. index.js is heavily obfuscated (obfuscator.io-style 317-entry RC4-encoded string array, base64 decoder, array-rotation self-shuffle, control-flow flattening) which hides the destination URL, AES key material, and command strings from any plain-text inspection. At runtime the script imports http/https, fs, path, os, crypto, and child_process, performs an HTTPS GET against a hard-coded remote host, splits the response on ':' into IV and ciphertext, decrypts via crypto.createDecipheriv('aes-256-...', <sha256-derived key>, Buffer.from(iv,'base64')), writes the decrypted bytes into path.join(os.tmpdir(), <name>) with flag 'w+', and immediately invokes the dropped file via child_process.exec/execFile with windowsHide: true. This is a fetch-decrypt-and-execute dropper firing on default install. The package name also leverages the popular express framework while shipping empty author/description/repository metadata and a generic README that itself notes the script is obfuscated — consistent with a deliberate supply-chain lure rather than a legitimate helper.

Malicious versions

2 flagged

12.1.912.1.10

Indicators of compromise (SHA-256)

1ba96d5070924af79839d4dbc950b28c3f59ad9515890cf83f1d631a6678c120

a8d292a4664135ed1869f907d62fb6472839ab54a59aedb2f3a88022a0c70095

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

Campaign

IN-MAL-2026-007670IN-MAL-2026-007671

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks express-initial-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