Which versions of encryptstringadmincore are malicious?

The following npm versions of encryptstringadmincore are flagged malicious: 1.0.1, 1.1.0. Treat any of these as compromised.

How do I remediate encryptstringadmincore if I installed it?

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

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

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

Malicious package

encryptstringadmincorenpm

encryptstringadmincore is a confirmed malicious npm package (MAL-2026-11013) that opens a backdoor for remote access (malicious versions 1.0.1, 1.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in encryptstringadmincore (npm)

MAL-2026-11013

Immediate action

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

npm uninstall encryptstringadmincore

What this malware does

The package's main module core.js is heavily obfuscated (obfuscator.io-style string-array with self-defending anti-debug and control-flow flattening) and contains a fetch-to-Function() pipeline that retrieves remote payloads and executes them in-process. Network sinks include api.jsonbin.io (accessed with X-Bin-Name headers and /config/ paths) and PubNub's ps.pndsn.com using hardcoded publish key pub-c-a17b9eb1-6275-474c-89fa-24e2f36632c3 and a sec-c-... secret key, forming both publish and subscribe URLs. Retrieved strings are passed to the JavaScript Function() constructor, giving whoever controls the referenced jsonbin bin or the PubNub channel arbitrary code execution on any host that require()s this package. The obfuscation exists to conceal the C2 endpoints and the network-to-exec dataflow; the stated 'encrypt string' purpose does not justify a remote code loader.

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

2 flagged

1.0.11.1.0

Indicators of compromise (SHA-256)

bee41f6acdd1724509277844381ea72ee9e814432afa535d4c382787d0cd5161

6fb9468e3d6f153d718527bb4350b6593d64b67cf16b5b81cdf56e4781d1b483

69db5d5ddd0bb81daa6c4b0af4fa7a34d8a8676330eaf7737653eef26ffd5462

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

Campaign

GHSA-hgfq-c4x3-jx2rIN-MAL-2026-010952IN-MAL-2026-012901

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks encryptstringadmincore-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