Which versions of https-emailjs are malicious?

Every published version of https-emailjs on npm is considered malicious. Remove the package entirely.

How do I remediate https-emailjs if I installed it?

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

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

Yes — https-emailjs is associated with the GHSA-3gjc-g7m2-vjf4 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 https-emailjs 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 https-emailjs (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging https-emailjs across your stack and pipelines.

Malicious package

https-emailjsnpm

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

MAL-2026-724

Immediate action

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

npm uninstall https-emailjs

What this malware does

The package https-emailjs was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

e6feff6e256b4c145082869f4ce5f64f2a2a15cab09caeef3e3d5735188aa0f6

d8aff232c81a7253eeb9e10075207aebc5908976a9a1adf6009d750b444467db

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

Campaign

GHSA-3gjc-g7m2-vjf4

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks https-emailjs-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