
Research
/Security News
Toptal’s GitHub Organization Hijacked: 10 Malicious Packages Published
Threat actors hijacked Toptal’s GitHub org, publishing npm packages with malicious payloads that steal tokens and attempt to wipe victim systems.
safer-eval
Advanced tools
a safer eval
A safer approach for eval in node and browser. Before using this module, ask
yourself if there are no better options than using saferEval.
It is potentially better than the bad old eval()
but still has some harmful potential.
Especially when it comes to passing context
props.
Use clones to wrap-up the methods you like to allow.
Checkout the "harmful context" tests section.
Warning: The
saferEval
function may be harmful - so you are warned!
In node the vm
module is used to sandbox the evaluation of code
.
The browser version browser.js
might not be as safe as the node version
index.js
as here no real sandboxing is available. Please consider modules like
sandboxr.
Runs on node and in modern browsers:
Versions | |
---|---|
node | |
Chrome | 55, 56 |
Firefox | 45, 51 |
Edge | 13, 14 |
IE | |
Safari | 10 |
iOS Safari | 10 |
npm install --save safer-eval
context
allows the definition of passed in Objects into the sandbox.
Take care, injected code
can overwrite those passed context props!
Check the tests under "harmful context"!
Parameters
code: String
, a string containing javascript code
context: Object
, define globals, properties for evaluation context
Returns: Any
, evaluated code
Example:
in node:
var saferEval = require('safer-eval')
var code = `{d: new Date('1970-01-01'), b: new Buffer('data')}`
var res = saferEval(code)
// => toString.call(res.d) = '[object Date]'
// => toString.call(res.b) = '[object Buffer]'
in browser:
var saferEval = require('safer-eval')
var code = `{d: new Date('1970-01-01'), b: function () { return navigator.userAgent }`
var res = saferEval(code, {navigator: window.navigator})
// => toString.call(res.d) = '[object Date]'
// => toString.call(res.b) = '[object Function]'
// => res.b() = "Mozilla/5.0 (..."
To minimize any harmful code injection carefully select the methods you allow in context
var code = `window.btoa('Hello, world')`
// AVOID passing a GLOBAL context!!!
var res = saferEval(code, {window: window})
// BETTER - code needs only access to window.btoa
const clones = require('clones')
var context = {
window: {
btoa: clones(window.btoa, window)
}
}
var res = saferEval(code ,context)
// => res = 'SGVsbG8sIHdvcmxk'
Use new SaferEval()
to reuse a once created context.
const {SaferEval} = require('safer-eval')
const safer = new SaferEval()
var code = `{d: new Date('1970-01-01'), b: new Buffer('data')}`
var res = safer.runInContext(code)
FAQs
harmful as eval
The npm package safer-eval receives a total of 18,075 weekly downloads. As such, safer-eval popularity was classified as popular.
We found that safer-eval demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
/Security News
Threat actors hijacked Toptal’s GitHub org, publishing npm packages with malicious payloads that steal tokens and attempt to wipe victim systems.
Research
/Security News
Socket researchers investigate 4 malicious npm and PyPI packages with 56,000+ downloads that install surveillance malware.
Security News
The ongoing npm phishing campaign escalates as attackers hijack the popular 'is' package, embedding malware in multiple versions.