# MAL-2026-11013: Malicious code in encryptstringadmincore (npm)


- **Type:** Malicious package
- **Package:** `encryptstringadmincore` (npm)
- **Published:** 22 Jul 2026
- **Also known as:** GHSA-hgfq-c4x3-jx2r

## What is MAL-2026-11013?

MAL-2026-11013 is a malicious package in encryptstringadmincore, published on 22 Jul 2026. 

### Official description

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.

## What should I do about MAL-2026-11013?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-11013 is a malicious package: encryptstringadmincore (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-11013/ (Markdown: https://insights.sbomify.com/MAL-2026-11013/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-11013

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-11013/
Summaries are generated and may contain mistakes; the official description above is the record.